public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A portage nuisance
Date: Sat, 28 Oct 2017 21:54:18 +0200	[thread overview]
Message-ID: <b113737a-dc04-4e3a-34ee-7bfff6b019ce@gmail.com> (raw)
In-Reply-To: <59F4C549.6010507@youngman.org.uk>

On 28/10/2017 19:58, Wols Lists wrote:
> On 28/10/17 15:52, Andrew Savchenko wrote:
>> On Fri, 27 Oct 2017 14:58:13 +0100 Peter Humphrey wrote:
>>>> On Fri, 27 Oct 2017 12:52:54 -0000
>>>> Helmut Jarausch <jarausch@skynet.be> wrote:
>>>>
>>>>>> I have a problem with emerge for a long time.
>>>>>> Sometimes I need to (re-)emerge many packages like in an
>>>>>> emerge --emptytree @world
>>>>>>
>>>>>> Because I use several overlays, there are problems with a lot of
>>>>>> packages.
>>>>>> Unfortunately, emerge shows me just the first problem (like a missing
>>>>>> USE-flags) and then terminates.
>>>>>> Is there any means to let emerge go and report several (all) problems
>>>>>> which are independent of each other?
>>>>
>>>> EMERGE_DEFAULT_OPTS="--keep-going" ?
>> No, --keep-going allows to continue as long as possible after a
>> build failure. Helmut asks about dependecies resolution failures,
>> e.g. in some package REQUIRED_USE is not met, or circular
>> dependency occurs and so on.
> 
> What I would like - a bit like --keep-going - is some option that tries
> again.
> 
> When I do an "emerge -u" it sometimes blows up with this massive load of
> dependency failures. So what I end up doing is emerge a few packages
> that look like they're going to work, and then try my full update again.
> After several cycles through this, suddenly everything works.
> 
> So my spec for what I would like is basically, as each package
> successfully resolves its dependencies, add it to a "try again" list. If
> the current list blows up in dependency hell, restart the emerge with
> just the packages in the "try again" list.


That is completely contrary to how portage is supposed to work and
produces an unpredictable result.

*You* know what you want and can do it, *you* are a human with a brain
who understands meaning.

Portage cannot do that, it is backed by silicon and has no concept of
meaning. So it has only one real choice - it can do it all or it does
not try.

I'm not surprised Zac never tried implementing partial graph resolution
for the very simple reason that if you try do it, you have no idea what
is going to be built. That is the opposite of what portage must deliver.
-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2017-10-28 19:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27 12:52 [gentoo-user] A portage nuisance Helmut Jarausch
2017-10-27 13:58 ` Peter Humphrey
2017-10-28 14:52   ` Andrew Savchenko
2017-10-28 17:58     ` Wols Lists
2017-10-28 19:54       ` Alan McKinnon [this message]
2017-10-28 20:39         ` Anthony Youngman
2017-10-28 20:50           ` Alan McKinnon
2017-10-28 21:59             ` Anthony Youngman
2017-10-28 22:45               ` Andrew Savchenko
2017-10-29  0:10                 ` Wols Lists
2017-10-29  0:58                   ` Michael Orlitzky
2017-10-27 15:18 ` Alan McKinnon

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=b113737a-dc04-4e3a-34ee-7bfff6b019ce@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@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