1 |
On Saturday 06 March 2010 10:19:19 Mark David Dumlao wrote: |
2 |
> Hi! |
3 |
> I'm wondering if anyone's written a script that looks deep into the |
4 |
> build dependencies of some package foo, and gives you a list of |
5 |
> ebuilds you need to unmask to build it. Immediate build dependencies |
6 |
> could easily be shown using the ebuild itself, and deep dependencies |
7 |
> could be shown using equery something, but I just want to focus on |
8 |
> dependencies you need to unmask when building. |
9 |
> |
10 |
> I usually just manually iterate through emerge -uDNtav world/something |
11 |
> to make something like that happen, and it's just hit me that this |
12 |
> sounds like a chore that's bound to have bugged someone. |
13 |
> |
14 |
> I'm not looking for a tool that writes my package.keywords/* for me, |
15 |
> I'd like to do that myself, but the iteration process is more painful |
16 |
> than it should be "manually". If there's none I was wondering what |
17 |
> kinds of challenges would it take to write one in python as that |
18 |
> sounds like a cool exercise to try out. |
19 |
|
20 |
Hmm, I was going to suggest autounmask, but since you don't want it to write |
21 |
your package.keywords/* for you point it to another file and then look at what |
22 |
it's written there. |
23 |
|
24 |
HTH. |
25 |
-- |
26 |
Regards, |
27 |
Mick |