From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH 0/5] drop dependency on GNOME if x11 is disabled
Date: Wed, 22 Feb 2012 13:31:14 +0000 [thread overview]
Message-ID: <1329917474.20261.142.camel@ted> (raw)
In-Reply-To: <1329910007-8441-1-git-send-email-obi@opendreambox.org>
On Wed, 2012-02-22 at 12:26 +0100, Andreas Oberritter wrote:
> I'd like to stop various GNOME packages from being built in a
> distro which doesn't use x11. For me, this fixes many unwanted
> dependencies, e.g. librsvg -> gconf -> polkit -> systemd -> udev-systemd
> on a system with an old kernel (2.6.18), which cannot use a recent
> udev. Of course, it saves some build time, too.
That dependency doesn't exist in OE-Core FWIW.
> I guess, additional PR bumps for all users of gconf, gnomebase and
> gtk-icon-cache bbclasses are required in order to pick up this change,
> right?
This is one of the few cases I'm tempted to say no, its not required.
> Does someone already have a script to automatically generate
> a list of affected recipes? Is the PR bump required, considering that
> this change mainly reduces build-time dependencies?
The plan is to rely on sstate's hash changes and the OEBasicHash
signature generator for this in future.
> It also disables
> some preinst and postrm hooks, but they don't really hurt on existing
> images.
I'd suggest for these we modify them to only run if the appropriate
executables are present. If not present, then it won't hurt anything.
> I suppose there aren't many images using GNOME packages
> without x11. Any opinions?
>
> Is it OK to use the 'x11' flag for this purpose? Is anybody using
> GNOME with a different backend? Would it be better to introduce
> a 'gnome' (and 'gconf'?) distro feature flag?
I looked at these patches and my conclusion was no, the x11 flag is not
appropriate in this context.
Why? It would break gtk+ compiled against directfb for example. In the
future we'll likely have a similar issue if gtk+ is compiled against
something like wayland.
I also don't like "gnome" since you are using some gnome packages.
Specifically, you seem to want to avoid gtk and gconf. So all things
considered this needs a bit more discussion...
Cheers,
Richard
next prev parent reply other threads:[~2012-02-22 13:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 11:26 [RFC][PATCH 0/5] drop dependency on GNOME if x11 is disabled Andreas Oberritter
2012-02-22 11:26 ` [PATCH 1/5] libsoup-2.4: don't depend on libgnome-keyring unless x11 is defined Andreas Oberritter
2012-02-22 12:56 ` Koen Kooi
2012-02-24 8:10 ` Khem Raj
2012-02-24 13:27 ` Andreas Oberritter
2012-02-24 15:05 ` Richard Purdie
2012-02-22 11:26 ` [PATCH 2/5] libproxy: don't depend on gconf " Andreas Oberritter
2012-02-22 12:57 ` Koen Kooi
2012-02-22 11:26 ` [PATCH 3/5] gconf.bbclass: don't add dependencies or hooks " Andreas Oberritter
2012-02-22 11:26 ` [PATCH 4/5] gtk-icon-cache.bbclass: " Andreas Oberritter
2012-02-22 11:26 ` [PATCH 5/5] gnomebase.bbclass: skip packages inheriting gnomebase " Andreas Oberritter
2012-02-22 13:31 ` Richard Purdie [this message]
2012-02-22 14:54 ` [RFC][PATCH 0/5] drop dependency on GNOME if x11 is disabled Andreas Oberritter
2012-02-22 15:00 ` Paul Eggleton
2012-02-22 21:24 ` Richard Purdie
2012-02-23 1:35 ` Andreas Oberritter
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=1329917474.20261.142.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox