From: Chris Elston <celston@katalix.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PROPOSAL] Package feature switches, redux.
Date: Mon, 04 Jul 2011 17:49:37 +0100 [thread overview]
Message-ID: <1309798177.20200.128.camel@desktop.home> (raw)
In-Reply-To: <4E11EDD1.1000308@slimlogic.co.uk>
On Mon, 2011-07-04 at 17:44 +0100, Graeme Gregory wrote:
> On 07/04/2011 05:12 PM, Chris Elston wrote:
> >> Hi, with my Angstrom cap on I like this syntax and I think it will be
> >> really useful.
> >>
> >> A second level concern I have is about conflicting features, its not
> >> something we will come across probably in DISTRO land as we are sensible
> >> enough not to select them. But users could select them in local.conf.
> >>
> >> Graeme
> > As a new developer, I've discovered that there are plenty of things that
> > you can set in local.conf which break things :D
> >
> > Could you please give an example of conflicting features that could
> > cause problems, I'm not experienced enough with OE to have encountered
> > that problem yet.
> >
> >
> Cant think of a solid one off the top of my head, but I mean the cases where
>
> --enable-feature means that --disable-another-feature is done.
>
> This is why I listed it as a secondary issue.
>
> Graeme
I understand. We could capture that information with an optional extra
field in the config info something like:
PACKAGE_CONFIG[foo] = "--enable-foo, --disable-foo, libfoo, <options
which conflict with foo>"
And then detect the conflict. It's a trade off of time to handle that
conflicts field, versus how many potential conflicts there are I guess.
I think we could add it later if it turned out to be a common problem.
Cheers,
Chris.
next prev parent reply other threads:[~2011-07-04 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 11:54 [PROPOSAL] Package feature switches, redux Chris Elston
2011-07-04 13:58 ` Richard Purdie
2011-07-06 18:15 ` Chris Elston
2011-07-04 15:43 ` Graeme Gregory
2011-07-04 16:12 ` Chris Elston
2011-07-04 16:44 ` Graeme Gregory
2011-07-04 16:49 ` Chris Elston [this message]
2011-07-18 21:20 ` Martin Jansa
2011-07-12 17:03 ` Mark Hatle
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=1309798177.20200.128.camel@desktop.home \
--to=celston@katalix.com \
--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