From: Michael 'Mickey' Lauer <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: USE flags mumbling
Date: Fri, 02 Jul 2010 00:33:46 +0200 [thread overview]
Message-ID: <1278023626.12473.22.camel@saphir> (raw)
In-Reply-To: <1278023342.4507.8.camel@lenovo.internal.reciva.com>
Am Donnerstag, den 01.07.2010, 23:29 +0100 schrieb Phil Blundell:
> On Thu, 2010-07-01 at 15:16 -0700, Tom Rini wrote:
> > One of the issues with some form of USE flags, and I believe this is one
> > of the big ones for Angstrom as well as any other public feed publishing
> > distribution is that having a single recipe that does different things
> > based on variables makes maintaining their feed (and allowing users to
> > publish their own compatible feeds) a nightmare.
>
> It's only a nightmare if the flags in question are user-frobbable. If
> they are all nailed down in the DISTRO configuration (which
> DISTRO_FEATURES certainly ought to be), and those folks who want to
> build compatible binaries just leave them alone, then there oughtn't to
> be any real problem. To that extent it doesn't really seem any
> different to the choice of compiler or tuning flags or glibc version or
> any of the other ways in which you can already produce incompatible
> binaries by flipping the wrong switches.
Agreed. I think we should be more open to this concept. At least for
packages with optional (but "infecting") X11 support -- such as EFL -- I
plan to use such a mechanism soon.
--
:M:
next prev parent reply other threads:[~2010-07-01 22:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 16:24 USE flags mumbling Graeme Gregory
2010-07-01 16:50 ` Chris Larson
2010-07-01 17:00 ` Graeme Gregory
2010-07-01 20:53 ` Koen Kooi
2010-07-01 22:12 ` Chris Larson
2010-07-01 22:16 ` Tom Rini
2010-07-01 22:19 ` Chris Larson
2010-07-01 22:29 ` Phil Blundell
2010-07-01 22:33 ` Michael 'Mickey' Lauer [this message]
2010-07-01 22:39 ` Tom Rini
2010-07-02 6:01 ` Roman I Khimov
2010-07-02 6:52 ` Koen Kooi
2010-07-02 10:28 ` Richard Purdie
2010-07-01 22:22 ` Tom Rini
2010-07-02 6:10 ` Michael Lippautz
2010-07-02 6:22 ` Martin Jansa
2010-07-02 15:45 ` Tom Rini
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=1278023626.12473.22.camel@saphir \
--to=mickey@vanille-media.de \
--cc=openembedded-devel@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