All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: USE flags mumbling
Date: Thu, 01 Jul 2010 22:53:24 +0200	[thread overview]
Message-ID: <i0iv84$7qt$1@dough.gmane.org> (raw)
In-Reply-To: <20100701172428.3b2ac88e@xora-desktop.xora.org.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01-07-10 18:24, 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?

Just that USE flags shouldn't be used if seperate recipes can solve it
as well.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMLQBEMkyGM64RGpERAikeAJ9L/lRCs6ZFrvBJfEszjZDEmlNIxQCeJURs
ag7eTOeSBZjR6IroPtaPKbE=
=USZM
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2010-07-01 20:58 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 [this message]
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
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='i0iv84$7qt$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.