3 ms·
You may be referring to paco[1], which has always been kind of a hack. It also appears to not have been updated in a very long time. 1: http://paco.sourceforge
by naner 14y ago
You may be referring to paco[1], which has always been kind of a hack. It also appears to not have been updated in a very long time.
1: http://paco.sourceforge.net/ http://paco.sourceforge.net/
- peterwwillis 14y agoPossibly... I don't remember the tool I saw using an LD_PRELOAD, and I think it operated on post-make-install files (like a DESTDIR staging directory). Anyway, the mini script I provided below is like half the functionality you would need after the source is compiled to a PREFIX of /opt/package/version/. Perhaps i'll write a tool when I get bored :-) The tool and method i'm borrowing from a proprietary tool I saw once, but obviously other people have implemented it too. Paco has a great idea though, and that's a meta-format and wrapper for different system packages. If you have to support five different production operating systems and the same software on all of them, switching between package managers is a pain in the ass. An extra tool to cross-reference paco to the OS's packages could make it really handy for resolving software updates in a unified way.