All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: USE flags mumbling
Date: Thu, 01 Jul 2010 15:22:54 -0700	[thread overview]
Message-ID: <4C2D153E.1040608@mentor.com> (raw)
In-Reply-To: <20100701172428.3b2ac88e@xora-desktop.xora.org.uk>

Graeme Gregory wrote:
> We already have BBCLASSEXTENDS which modifies ${PN} of a package and
> can use overrides to change behaviors of recipes.
> 
> Maybe USE flags could be implemented in a similar fashing.
> 
> DISTRO_USE = "nossl nox11"
> 
> EXTRA_OECONF_append_use-nossl = "--disable-ssl"
> 
> ${PN} of the recipe becomes XXXX-nossl
> 
> Thoughts?

First we'd have to have a discussion on what the default should be and 
get agreement everywhere (ssl? x11? bluetooth (bluez3? bluez4?)? alsa?) 
on the whole raft of things that it would be nice to globally turn off 
or on.  Then we have to know which ones a given recipe actually made use 
of as opkg-nox11 is quite silly but conversely it'd be quite nice to 
have in autotools.bbclass the magic to always pass --disable-x11 (since 
it sure feels like everyone uses the same enable/disable switch finally).

Second, we also need a raft of, and perhaps a much easier way to, add 
binary package output virtuals.

I wonder, and I have to admit to having no real gentoo background here, 
how do they solve this problem?  Did they invent their own package 
format and add another field that consists of use flags?  That'd make 
some stuff a lot easier, but making deb/rpm get that mapping somehow 
seems hard at first.

-- 
Tom Rini
Mentor Graphics Corporation



  parent reply	other threads:[~2010-07-01 22:27 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
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 [this message]
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=4C2D153E.1040608@mentor.com \
    --to=tom_rini@mentor.com \
    --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 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.