public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Re: Dynamic USE dependencies
Date: Wed, 8 Apr 2015 06:13:36 -0400	[thread overview]
Message-ID: <CAGfcS_nzwsJOfy=iniNi3MFsLFCKUPM5XBQ2Y6-eCu6xgAcX1g@mail.gmail.com> (raw)
In-Reply-To: <mg2mb5$e1$1@ger.gmane.org>

On Wed, Apr 8, 2015 at 3:45 AM, Martin Vaeth <martin@mvath.de> wrote:
> Rich Freeman <rich0@gentoo.org> wrote:
>>
>> Keep in mind that keeping track of past decisions made by portage does
>> not require user-editable config files in /etc.
>
> Yes, but you might not always agree with portage's decisions,
> and the resolution might be non-unique.

How is this different with USE flags vs package installs?  The
satisfaction of virtuals could have many possible solutions.  We make
it deterministic by defaulting to the first option listed for the
first package that happens to get installed.  If you install a series
of packages in various orders from a fresh install, you could get
different packages installed to satisfy virtuals.

The solution we provide for package installs is that the user can just
emerge a dependency manually if they have a preference, and then
portage will stick with it unless there is a conflict.

For dynamic USE flags I've already proposed two mechanisms to give the
user control:
1.  They can STILL populate /etc/portage/package.use and make explicit
choices, which portage will follow.
2.  They could manually install a package with one-time specified USE
flags, and portage would stick with these as long as they don't create
a conflict.

Why do we need another mechanism to control what flags a package gets
installed with other than these two, such as making more detailed
cache data user-editable?

-- 
Rich


  reply	other threads:[~2015-04-08 10:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 16:32 [gentoo-portage-dev] Dynamic USE dependencies Rich Freeman
2015-04-02 16:56 ` Kent Fredric
2015-04-02 17:32   ` Rich Freeman
2015-04-02 18:03     ` Kent Fredric
2015-04-02 19:34       ` Rich Freeman
2015-04-03  2:10 ` [gentoo-portage-dev] " Duncan
2015-04-03  2:26   ` Rich Freeman
2015-04-03  6:38     ` Duncan
2015-04-03  6:59       ` Brian Dolbec
2015-04-03 11:52         ` Duncan
2015-04-03 13:31           ` Brian Dolbec
2015-04-05  5:03             ` Duncan
2015-04-05  5:48 ` [gentoo-portage-dev] " Zac Medico
2015-04-05 15:47   ` [gentoo-portage-dev] " Martin Vaeth
2015-04-05 16:13     ` Rich Freeman
2015-04-06 12:02       ` Martin Vaeth
2015-04-06 13:08         ` Rich Freeman
2015-04-08  7:45           ` Martin Vaeth
2015-04-08 10:13             ` Rich Freeman [this message]
2015-04-08 14:21               ` Martin Vaeth

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='CAGfcS_nzwsJOfy=iniNi3MFsLFCKUPM5XBQ2Y6-eCu6xgAcX1g@mail.gmail.com' \
    --to=rich0@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