From: Ned Ludd <solar@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Cc: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
Subject: Re: [gentoo-portage-dev] allow people to disambiguate built_with_use in upgrade situations
Date: Tue, 16 Jan 2007 16:30:50 -0800 [thread overview]
Message-ID: <1168993850.1871.15.camel@onyx.private.gni.com> (raw)
In-Reply-To: <200701161906.22307.vapier@gentoo.org>
On Tue, 2007-01-16 at 19:06 -0500, Mike Frysinger wrote:
> Diego is proposing a new flag to built_with_use to handle the corner case
> where you query a package that does not have the requested flag in IUSE
>
> built_with_use [--missing <action>] ...
>
> so in the case of version transitions, you can specify the <action> as either
> true, false, or die (only current option)
>
> seems like a cleaner solution than forcing what can be a rats nest of
> has_version checks
> -mike
I'd agree. The built_with_use is a thorn in the side with the existing
behavior. Adding --missing yes|no 0|1 would be nice.
--
Ned Ludd <solar@gentoo.org>
Gentoo Linux
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-17 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 0:06 [gentoo-portage-dev] allow people to disambiguate built_with_use in upgrade situations Mike Frysinger
2007-01-17 0:30 ` Ned Ludd [this message]
2007-01-19 5:29 ` Mike Frysinger
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=1168993850.1871.15.camel@onyx.private.gni.com \
--to=solar@gentoo.org \
--cc=flameeyes@gentoo.org \
--cc=gentoo-portage-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