From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] libgphoto2-2.4.10 news item
Date: Mon, 14 Feb 2011 19:25:27 +0100 [thread overview]
Message-ID: <1297707927.7123.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20110214134147.5047e2aa@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
El lun, 14-02-2011 a las 13:41 +0000, Ciaran McCreesh escribió:
> On Mon, 14 Feb 2011 14:33:52 +0100
> Pacho Ramos <pacho@gentoo.org> wrote:
> > > You should be able to -* them out... -* is fine (assuming Portage
> > > handles it) since we know what the null set is; it's just * that's
> > > the problem.
> >
> > Yeah, portage handles it, but thought -* also had the same problem,
> > thanks for clarifying, anyway, latest approach on only enable ptp2 by
> > default looks fine for me
>
> No, -* is fine, so long as Portage doesn't pass it through literally.
>
> The problem, specifically, is that things like this are totally legal
> and are done by some packages:
>
> IUSE="linguas_en linguas_fr"
>
> if use linguas_de ; then
>
> if has linguas_de $LINGUAS ; then
>
> if has linguas_de $USE ; then
>
> So if you were to set LINGUAS="*", there would have to be some magic
> way for the package mangler to know that linguas_de exists, even if
> there's no mention of it anywhere in any user config files or in IUSE
> (and no, the desc files aren't a complete list either).
>
> The reason for this, historically, was that IUSE was used purely for
> display purposes by Portage, whilst USE was worked out from everything
> in config files, regardless of whether or not the ebuild claimed to use
> it. That meant there was absolutely nothing stopping you from making
> IUSE incomplete...
>
Ah, thanks for the explanation. Regards
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-02-14 18:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 17:03 [gentoo-dev] libgphoto2-2.4.10 news item Pacho Ramos
2011-02-13 17:09 ` Ciaran McCreesh
2011-02-13 17:16 ` Pacho Ramos
2011-02-13 19:31 ` Pacho Ramos
2011-02-13 19:34 ` Ciaran McCreesh
2011-02-13 20:00 ` Pacho Ramos
2011-02-13 20:17 ` Ciaran McCreesh
2011-02-14 9:07 ` [gentoo-dev] " Duncan
2011-02-14 13:17 ` Ciaran McCreesh
2011-02-14 10:35 ` [gentoo-dev] " Pacho Ramos
2011-02-14 13:21 ` Ciaran McCreesh
2011-02-13 20:00 ` Matthew Summers
2011-02-13 20:08 ` Pacho Ramos
2011-02-14 10:15 ` Pacho Ramos
2011-02-14 10:24 ` Gilles Dartiguelongue
2011-02-14 10:34 ` Pacho Ramos
2011-02-14 10:37 ` Gilles Dartiguelongue
2011-02-14 10:40 ` Pacho Ramos
2011-02-14 10:42 ` Pacho Ramos
2011-02-14 10:53 ` Gilles Dartiguelongue
2011-02-14 13:19 ` Ciaran McCreesh
2011-02-14 13:33 ` Pacho Ramos
2011-02-14 13:41 ` Ciaran McCreesh
2011-02-14 18:25 ` Pacho Ramos [this message]
2011-02-14 10:41 ` Ulrich Mueller
2011-02-14 10:53 ` Pacho Ramos
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=1297707927.7123.30.camel@localhost.localdomain \
--to=pacho@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