From: Adrian Bunk <bunk@stusta.de>
To: "Hongxu Jia" <hongxu.jia@windriver.com>,
"Andreas Müller" <schnitzeltony@gmail.com>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: RFC: Add DISTRO_FEATURES(xfce) to control meta-xfce
Date: Fri, 28 Jun 2019 15:58:45 +0300 [thread overview]
Message-ID: <20190628125845.GA5313@localhost> (raw)
In-Reply-To: <fc78dc28-bc7c-2433-871f-3eb5047a0ee8@windriver.com>
On Fri, Jun 28, 2019 at 10:20:36AM +0800, Hongxu Jia wrote:
> Hi all,
>
> Currently, I am improving OE to follow Yocto Project Compatible,
> One rule of Yocto Project Compatible is when a new layer is added,
> it should not affect other layer, but unfortunately, bbappend in
> meta-xfce broke the rule.
>
> So I suggest to add DISTRO_FEATURES(xfce) as a switch to control,
> in short term, we could use it to control bbappend in meta-xfce,
> in long term, we could use it to control more xfce specific features
>
> (As a alternative way, I also tried to remove bbappend directly,
> but I found the existence of bbappend is indeed necessary)
blueman upstream defaults to installing the files for thunar-sendto.
Andreas, was there any specific reason why you made this conditional
instead of keeping it enabled unconditional with only an RSUGGESTS
on thunar?
gdmflexiserver looks like a workaround for something that should be
fixed properly instead to me.
But short-term adding it to the normal lxdm recipe in meta-oe might
be an options?
> //Hongxu
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-06-28 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 2:20 RFC: Add DISTRO_FEATURES(xfce) to control meta-xfce Hongxu Jia
2019-06-28 12:58 ` Adrian Bunk [this message]
2019-06-28 14:23 ` Hongxu Jia
2019-07-01 12:48 ` Adrian Bunk
2019-07-02 1:23 ` Hongxu Jia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190628125845.GA5313@localhost \
--to=bunk@stusta.de \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=schnitzeltony@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.