public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A portage nuisance
Date: Sat, 28 Oct 2017 20:58:30 -0400	[thread overview]
Message-ID: <8ad8a296-ee1b-b9dd-73e2-13b767ab70aa@gentoo.org> (raw)
In-Reply-To: <59F51C5B.40609@youngman.org.uk>

On 10/28/2017 08:10 PM, Wols Lists wrote:
> 
> In other words, I'm asking emerge to automate what I do - look at the
> output, find a subset of packages that I think will work, and then ask
> it to try again with just those packages. I would be very surprised if
> it iterated repeatedly down to the null set.

This should be possible. I've lovingly referred to this option in the
past as something like "emerge --just-fucking-do-anything". I can have
300 packages in my update list, with a bunch of installed stuff
depending on a masked version of ruby, and a package that needs to be
manually uninstalled, and new REQUIRED_USE conflicts, and subslot
rebuilds of things that are now masked, and...

And yet portage still knows that timezone-data is going to get updated.
If I can look through the list and "emerge -1 timezone-data" and have
that work, then portage should be able to figure that out, too. No
matter how long it takes, it can't be slower than me doing it by hand.


  reply	other threads:[~2017-10-29  0:58 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
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 [this message]
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=8ad8a296-ee1b-b9dd-73e2-13b767ab70aa@gentoo.org \
    --to=mjo@gentoo.org \
    --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