revdep-rebuild --library foo.so.1 --library bar.so.1
* searches only for bar.so.1
revdep-rebuild --library foo.so.1 bar.so.1
* searches only for foo.so.1
It's not obvious and the man page suggest:
revdep-rebuild [OPTIONS] [--] [EMERGE OPTIONS]
so there isn't anything that implies it will take only one --library argument.
In fact preserve_old_lib in eutils.eclass has been designed to reflect this shortcoming by suggesting multiple revdep-rebuild calls even when it does accept multiple file arguments itself.
You are reading my mind. I was just thinking the same thing. I'm going to target it for 0.3.1. If it turns out to be trivial enough, we can backport it to 0.3.0
FWIW -- One of the examples the man page gives for revdep-rebuild is:
To rebuild packages that depend upon libImlib.so and libImlib2.so:
revdep-rebuild --library libImlib*.so.*
The actual behavior is to run 'revdep-rebuild' for the first library found.
I had wanted to run:
revdep-rebuild -i -p --library /usr/lib64/python2.6/site-packages/PyQt4/*.so
'revdep-rebuild' ran only for:
* Configuring search environment for revdep-rebuild
* Checking reverse dependencies
* Packages containing binaries and libraries using /usr/lib64/python2.6/site-packages/PyQt4/Qsci.so
* will be emerged.
Am I correct in assuming that this bug is opened for a different aspect of the same problem I encountered? i.e.: When using the --library flag, revdep-rebuild only works for a single library despite the example in the man page?
Slightly different issue and it looks like it got broken when we rewrote revdep-rebuild.
I'm going to open a separate bug.
(In reply to comment #3)
> Slightly different issue and it looks like it got broken when we rewrote
> I'm going to open a separate bug.
Thank you for the quick reply and thank you for including me on bug# 346475.
*** Bug 386649 has been marked as a duplicate of this bug. ***