1 |
Hi, |
2 |
|
3 |
Is there a better way to get a picture of the dependency tree that |
4 |
emerge walks? For example, when one wishes to unmask a package, it is |
5 |
possible that that package is itself dependent on other packages that |
6 |
require unmasking, and so on and so on. |
7 |
|
8 |
It's a little annoying having to: |
9 |
emerge -uDp world |
10 |
then |
11 |
echo foo-bar/baz >> /etc/portage/package.unmask |
12 |
then |
13 |
emerge -uDp world |
14 |
then |
15 |
echo qux-quux/corge >> /etc/portage/package.unmask |
16 |
|
17 |
Until all dependencies have been met. |
18 |
|
19 |
Are there any tricks or tips on how best to do this time-saving wise? |
20 |
Could the results be somehow cached so that subsequent runs are quicker? |
21 |
Or could the dependency tree be viewed somehow, so that the list of |
22 |
packages to unmask could be done in one step? |
23 |
|
24 |
Regards, |
25 |
|
26 |
--ibz. |
27 |
|
28 |
-- |
29 |
gentoo-dev@g.o mailing list |