package management... just an idea...
tushar at linuxfromscratch.org
Sun Jan 19 21:06:43 PST 2003
Tushar Teredesai wrote:
> Oneyed at gmx.de wrote:
>> ok, you all know ldd. so why shouldn't we call ldd for just every
>> executabl/library we find on the system and record the output in a
>> database? so we could track depencies: we will always know, which
>> library is needed by which program. there would be also the
>> possibility to define packages: a couple of binaries/libraries belong
>> to a package called somehow. an example: you've installed openssl
>> 0.9.6x and want to upgrade to 0.9.7 (due a security hole in 0.9.6g).
>> with such a tool you could find out, which programs depend on the
>> openssl 0.9.6 libraries.
>> it would also help you to find unused old libraries: if no program is
>> linked to the library, you can delete it.
>> erm. ok, it's just some kind of idea. this would be a lot of codework
>> to be done... so what do you think?
> Yep, I use that along with the pkg-user hint, that way I know which
> libraries the pkg depends on. I build a database of such dependencies
> and use that to figure out which pkgs to recompile in case I upgrade
> some package (an recompile is not always neccessary).
Just a note, this won't give you a complete list of dependencies, for
* libraries that are linked in statically
* packages that use other binaries
> To gain more dependency information, I use strace.
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe blfs-support' in the subject header of the message
More information about the blfs-support