Recently, revdep-rebuild has been moved to use /var/cache/revdep-rebuild instead of $HOME for its files. I spent a lot of time for knowing the new location and finally discovered it in bug 203414
I think that a bit more info to users should be shown when updating to new gentoolkit. There are two options:
1. Add an "einfo" message to ebuild warning about this change (seems easier way)
2. Modify revdep-rebuild to show FULL path to *.rr files when it fails or Ctrl+C is pressed
Thanks a lot
It tells you where the files are if you use the --verbose (-v) option.
(In reply to comment #1)
> It tells you where the files are if you use the --verbose (-v) option.
I didn't try to run it with "-v" :-S, sorry, anyway, message is shown at top of output, this is not too useful because a lot of other output is shown after it preventing me from reading the message if I don't scroll up (if I am able to)
I think that message should be shown at end instead of top when run with -v
Thanks again :-)
gentoolkit-0.2.4.1 will be in the tree after the tar file gets to the mirrors. Here is the output from elog for the new ebuild:
The default location for revdep-rebuild files has been moved
to /var/cache/revdep-rebuild when run as root.
Another alternative to equery is app-portage/portage-utils
For further information on gentoolkit, please read the gentoolkit
Well, thanks a lot :-D
Anyway, what about message informing about *.rr files location shown at first of "revdep-rebuild -v" output instead of start?
If it's too hard to modify feel free to leave it has current of course :-)
*** Bug 241832 has been marked as a duplicate of this bug. ***
*** Bug 243304 has been marked as a duplicate of this bug. ***
Paul Varner, i can not consider Bug 243304 as dup of this one. 236378 and 241832 ask for a message at runtime; when 243304 asks for a man page update. Those ones are about application output messages; my bug report is about documentation update.
And Since -v already provide the information, 236378 and 241832 should be marked invalid, when my bug is somehow a "completely different matter". But, i will not undo what you just did (ark my bug as dup), in case you disagree with my point of view.
None of the bugs are invalid, they are all about shortcomings in the documentation (which includes man pages) about where to find the revdep-rebuild files.
In my opinion this bug is overkill -- There're three places that denote the location of the new *.rr files:
- the man page
- the einfo after emerge gentoolkit
- the output of revdep-rebuild --verbose
Considering that this move to /var/cache is permanent we can assume users will eventually become used to it. The current (nonverbose) output is pretty, functional, and should last several more revisions of r-r, but the change required by this bug would be temporary and a maintenance issue.
I'm in favor of not fixing this bug.
(In reply to comment #9)
> In my opinion this bug is overkill -- There're three places that denote the
> location of the new *.rr files:
> - the man page
Wrong, i just checked again: this is NOT mentionned in man page; see my comment 7.
I agree to close bug 236378, but I ask reopen of Bug 243304 .
(In reply to comment #10)
> Wrong, i just checked again: this is NOT mentionned in man page; see my comment
> I agree to close bug 236378, but I ask reopen of Bug 243304 .
Oops, you're right. Done as requested.
Anyway, show the message at end instead of start of revdep-rebuild -v output would be much useful