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
Cc: Mark David Dumlao <madumlao@gmail.com>
Subject: Re: [gentoo-user] Any nice tools for emerge dependency resolution listing?
Date: Sat, 6 Mar 2010 13:46:46 +0200	[thread overview]
Message-ID: <201003061346.46936.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <6e2210231003060219u69cba62dle9b8c0c4a4661364@mail.gmail.com>

On Saturday 06 March 2010 12:19:19 Mark David Dumlao wrote:
> Hi!
> I'm wondering if anyone's written a script that looks deep into the
> build dependencies of some package foo, and gives you a list of
> ebuilds you need to unmask to build it. Immediate build dependencies
> could easily be shown using the ebuild itself, and deep dependencies
> could be shown using equery something, but I just want to focus on
> dependencies you need to unmask when building.
> 
> I usually just manually iterate through emerge -uDNtav world/something
> to make something like that happen, and it's just hit me that this
> sounds like a chore that's bound to have bugged someone.
> 
> I'm not looking for a tool that writes my package.keywords/* for me,
> I'd like to do that myself, but the iteration process is more painful
> than it should be "manually". If there's none I was wondering what
> kinds of challenges would it take to write one in python as that
> sounds like a cool exercise to try out.

Have you looked at autounmask?

Does it do what you need?

-- 
alan dot mckinnon at gmail dot com



  parent reply	other threads:[~2010-03-06 11:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-06 10:19 [gentoo-user] Any nice tools for emerge dependency resolution listing? Mark David Dumlao
2010-03-06 11:45 ` Mick
2010-03-06 11:46 ` Alan McKinnon [this message]
2010-03-06 11:53 ` Daniel Wagener
2010-03-06 14:10   ` Mark David Dumlao
2010-03-06 19:15     ` Dale
2010-03-07  5:01       ` Mark David Dumlao
2010-03-07  5:30         ` Dale

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=201003061346.46936.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=madumlao@gmail.com \
    /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