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