1 |
Duncan schrieb am 16.12.2008 00:47: |
2 |
> Paul Varner <fuzzyray@g.o> posted |
3 |
> 1229371818.21630.7.camel@××××××××××××××××××××××.com, excerpted below, on |
4 |
> Mon, 15 Dec 2008 14:10:17 -0600: |
5 |
> |
6 |
>> # Paul Varner <fuzzyray@g.o> (14 Dec 2008) # Dead upstream, |
7 |
>> masked for removal in ~30 to 60 days. app-portage/udept |
8 |
>> |
9 |
>> Additionally, it doesn't play well with EAPI's greater than zero. |
10 |
>> |
11 |
>> The removal bug is Bug #250839. If upstream comes back alive or someone |
12 |
>> forks and actively maintains, I will unmask or re-add to the tree. |
13 |
> |
14 |
> Ouch! This one hurts! |
15 |
|
16 |
++ |
17 |
|
18 |
I really hope someone steps up and continues maintaining this great |
19 |
tool. Before EAPI's greater than zero existed this tool combined many |
20 |
things I needed for daily use within one single application. |
21 |
|
22 |
> The main thing I use it for, and therefore the question I have about any |
23 |
> useful substitute, is quickly getting a changelog when portage won't spit |
24 |
> one out. In particular, when there's a USE flag change in an existing |
25 |
> package, or a downgrade, emerge --log won't output anything, because it's |
26 |
> not an upgrade. However, I find the info in such logs often useful! |
27 |
> |
28 |
> Of course I can check the package category and type in the whole long |
29 |
> path to the changelog and edit/head/view it by hand, but a quick dep -j |
30 |
> <pkg> is a lot faster and very useful! |
31 |
> |
32 |
> While I'm at it, is there anything useful to display metadata.xml? In |
33 |
> particular, the long descriptions and use flags can be useful. With |
34 |
> use.desc and especially the local version thereof going deprecated, and |
35 |
> with additional info about global flags sometimes in the metadata... |
36 |
|
37 |
Regarding metadata.xml there is (besides querying Willikins on IRC) |
38 |
emeta. Take a look at bug 248278 [1]. |
39 |
|
40 |
[1] http://bugs.gentoo.org/show_bug.cgi?id=248278 |