1 |
Hey Jason, |
2 |
|
3 |
As you know, I'm currently working on a tool to manage /etc/portage |
4 |
easily, to help users. Tentatively named emod, it has the synopsis |
5 |
|
6 |
emod mask|unmask|keyword|inject [--include-deps] [--category] blah1 |
7 |
blah2... |
8 |
|
9 |
Well, for the first optional argument, emod needs access to portage's |
10 |
dependency information. It would need to know what versions the package |
11 |
depended on, whether those packages could be sastified by "keyword" |
12 |
instead of "~keyword", and if emod is at one point extended to combine |
13 |
the functionality of euse, ie adding an |use mode, it would also need |
14 |
access to every package's dependencies IUSE settings to determine |
15 |
whether or not the given use was valid for deps. |
16 |
|
17 |
Thats all I can think of for right now, if I come up with more I'll let |
18 |
you know. |
19 |
|
20 |
Mike Tindal |