1 |
On Mon, Sep 19, 2011 at 4:33 PM, Mark Knecht <markknecht@×××××.com> wrote: |
2 |
> On Mon, Sep 19, 2011 at 7:36 AM, Michael Mol <mikemol@×××××.com> wrote: |
3 |
>> On Mon, Sep 19, 2011 at 10:20 AM, Allan Gottlieb <gottlieb@×××.edu> wrote: |
4 |
> <SNIP> |
5 |
>>> ajglap gottlieb # revdep-rebuild; revdep-rebuild --library '/usr/lib64/libpng14.so.14' |
6 |
> <SNIP> |
7 |
>> |
8 |
>> Is there no automated way to catch these? --library expects an |
9 |
>> argument; how do I know which libraries to feed it? |
10 |
> |
11 |
> My question exactly. It's not likeyou can look at just names of |
12 |
> libraries as I think to do this right you've got to look at every |
13 |
> revision of every library on the system, don't you? |
14 |
> |
15 |
> It's possible that this problem could exist for a long while if a |
16 |
> program doesn't get used much... |
17 |
|
18 |
Based on subsequent discussion since I wrote that question, I think |
19 |
the answer is, "currently, no." Ebuillds would need more metadata, and |
20 |
portage would need to be more aware of deep dependencies. |
21 |
|
22 |
I'm not sure of revdep-rebuild's angle, or how it might be able to be |
23 |
improved to detect errors that don't come from broken linkage. |
24 |
-- |
25 |
:wq |