public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ibraheem Umaru-Mohammed <iumarumohammed@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Tips/Tricks to avoid repetitively running 'emerge --pretend'?
Date: Sun, 19 Sep 2004 14:59:44 +0100	[thread overview]
Message-ID: <1095602384.22400.5.camel@rabox> (raw)

Hi, 

Is there a better way to get a picture of the dependency tree that
emerge walks? For example, when one wishes to unmask a package, it is
possible that that package is itself dependent on other packages that
require unmasking, and so on and so on. 

It's a little annoying having to: 
    emerge -uDp world 
then 
    echo foo-bar/baz >> /etc/portage/package.unmask 
then 
    emerge -uDp world 
then 
    echo qux-quux/corge >> /etc/portage/package.unmask 

Until all dependencies have been met. 

Are there any tricks or tips on how best to do this time-saving wise?
Could the results be somehow cached so that subsequent runs are quicker?
Or could the dependency tree be viewed somehow, so that the list of
packages to unmask could be done in one step? 

Regards, 

            --ibz.

--
gentoo-dev@gentoo.org mailing list


                 reply	other threads:[~2004-09-19 13:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1095602384.22400.5.camel@rabox \
    --to=iumarumohammed@gmail.com \
    --cc=gentoo-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