On Sun, 31 Aug 2014 10:56:21 -0400 "Anthony G. Basile" <bluen...@gentoo.org> wrote:
> On 08/31/14 08:43, Ciaran McCreesh wrote: > > On Sun, 31 Aug 2014 08:38:00 -0400 > > "Anthony G. Basile" <bluen...@gentoo.org> wrote: > >> Not exactly. The point is to *standardize* what is meant by "all > >> information" so that all package managers export the same minimum > >> set of information. The most important being NEEDED.ELF.2 which is > >> portage's VDB but not paludis. Also, it can be in any format and > >> exported in any way so long as it is well documented. The goal is > >> to have tools other than PM's make use of this information. The > >> example that began this is revdep-pax which uses NEEDED.ELF.2 to > >> trace out linking so as to migrate PaX flags between ELF objects. > > VDB is completely non-standard, undocumented, and hard to read > > correctly. There's no point in having information if you aren't > > allowed to use it. > > > > VDB as exported by portage is readable and useful to non-PM tools. > I'd give you a link to git.gentoo.org/proj/elfix as a concrete > example, but the site is still down. This usefulness suggests that > it should be standardize and documented so that VDB information can > be read correctly by non-PM tools. > +1 The new python based revdep-rebuild also uses scanelf and subsequently the NEEDED.ELF.2 files. And there are other tools that make use of vdb info. It is past due to have a minimum set of defined info to be recorded in the vdb. -- Brian Dolbec <dolsen>
