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: Mon, 6 Apr 2015 09:08:16 -0400	[thread overview]
Message-ID: <CAGfcS_=rAoJdU4m2wEOmGg_cnfMi7OwQU4moFjYH8_4OC_bBhw@mail.gmail.com> (raw)
In-Reply-To: <mftsjr$v62$1@ger.gmane.org>

On Mon, Apr 6, 2015 at 8:02 AM, Martin Vaeth <martin@mvath.de> wrote:
> My suggestion is something in between - less invasive
> (and, in particular, less time consuming)
> than your suggestion to recalculate the USE-settings
> with every emerge, but more automatic than the current state.

Keep in mind that keeping track of past decisions made by portage does
not require user-editable config files in /etc.  It just requires a
cache of some kind, much as we do with installed packages/etc.

That said, portage still has to spend time basically re-validating the
consistency of the entire system because we allow the use of overlays
and other situations that don't guarantee that portage will have some
kind of consistent pre-calculated depgraph handed to it.  If we
required all repositories to have some kind of pre-generated cache in
them and ensured that this was always up-to-date and better controlled
the kinds of dependency changes we made, then maybe there might be an
opportunity to offload some of the work to the repository level
instead of doing it on every Gentoo system.  Still, unless we banned
overlays I'm not sure how much even this would buy you, since you'd
have many of these that need to be merged somehow.

From Zac's email and other discussions in the past it seems like we're
basically committed to doing all these calculations all the time
anyway, so we shouldn't be too shy about taking advantage of them.

-- 
Rich


  reply	other threads:[~2015-04-06 13:08 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 [this message]
2015-04-08  7:45           ` Martin Vaeth
2015-04-08 10:13             ` Rich Freeman
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_=rAoJdU4m2wEOmGg_cnfMi7OwQU4moFjYH8_4OC_bBhw@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