From: "Tomáš Chvátal" <scarabeus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: package.use.stable.mask
Date: Sat, 10 Oct 2009 22:58:48 +0200 [thread overview]
Message-ID: <200910102258.48425.scarabeus@gentoo.org> (raw)
In-Reply-To: <4AD0F39D.8060007@gentoo.org>
Zac Medico wrote:
> Maybe a syntax extension for IUSE would be a little nicer. For example:
>
> IUSE="unstable? ( foo bar )"
>
> You could emulate this sort of extension in current EAPIs by simply
> adding IUSE="unstable" and then using that flag to conditionally
> disable things in *DEPEND, SRC_URI, and ebuild shell code.
> ,
That is another possibility but i tried to have something that is notdependant
on IUSE.
Because when you have it depending on iuse you will have to alter the ebuild
in future anyway, when the depending library will get OK.
It could be nice solution until we can launch support for the above file :]
Tom
next prev parent reply other threads:[~2009-10-10 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 20:04 [gentoo-dev] RFC: package.use.stable.mask Tomáš Chvátal
2009-10-10 20:50 ` Zac Medico
2009-10-10 20:58 ` Tomáš Chvátal [this message]
2009-10-10 21:14 ` Maciej Mrozowski
2009-10-11 6:55 ` Joshua Saddler
2009-10-11 9:16 ` Tomáš Chvátal
2009-10-11 9:46 ` [gentoo-dev] " Duncan
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=200910102258.48425.scarabeus@gentoo.org \
--to=scarabeus@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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