| 1 |
Paul Varner <fuzzyray@g.o> posted |
| 2 |
1229371818.21630.7.camel@××××××××××××××××××××××.com, excerpted below, on |
| 3 |
Mon, 15 Dec 2008 14:10:17 -0600: |
| 4 |
|
| 5 |
> # Paul Varner <fuzzyray@g.o> (14 Dec 2008) # Dead upstream, |
| 6 |
> masked for removal in ~30 to 60 days. app-portage/udept |
| 7 |
> |
| 8 |
> Additionally, it doesn't play well with EAPI's greater than zero. |
| 9 |
> |
| 10 |
> The removal bug is Bug #250839. If upstream comes back alive or someone |
| 11 |
> forks and actively maintains, I will unmask or re-add to the tree. |
| 12 |
|
| 13 |
Ouch! This one hurts! |
| 14 |
|
| 15 |
The main thing I use it for, and therefore the question I have about any |
| 16 |
useful substitute, is quickly getting a changelog when portage won't spit |
| 17 |
one out. In particular, when there's a USE flag change in an existing |
| 18 |
package, or a downgrade, emerge --log won't output anything, because it's |
| 19 |
not an upgrade. However, I find the info in such logs often useful! |
| 20 |
|
| 21 |
Of course I can check the package category and type in the whole long |
| 22 |
path to the changelog and edit/head/view it by hand, but a quick dep -j |
| 23 |
<pkg> is a lot faster and very useful! |
| 24 |
|
| 25 |
While I'm at it, is there anything useful to display metadata.xml? In |
| 26 |
particular, the long descriptions and use flags can be useful. With |
| 27 |
use.desc and especially the local version thereof going deprecated, and |
| 28 |
with additional info about global flags sometimes in the metadata... |
| 29 |
|
| 30 |
-- |
| 31 |
Duncan - List replies preferred. No HTML msgs. |
| 32 |
"Every nonfree program has a lord, a master -- |
| 33 |
and if you use the program, he is your master." Richard Stallman |
Archives