Gentoo Archives: gentoo-dev

From: "Anthony G. Basile" <blueness@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] RFC: GLEP 64: Standardize contents of VDB and establish and API for exporting this information.
Date: Sun, 31 Aug 2014 14:53:41
Message-Id: 54033795.9070606@gentoo.org
In Reply to: Re: [gentoo-dev] RFC: GLEP 64: Standardize contents of VDB and establish and API for exporting this information. by Ciaran McCreesh
1 On 08/31/14 08:43, Ciaran McCreesh wrote:
2 > On Sun, 31 Aug 2014 08:38:00 -0400
3 > "Anthony G. Basile" <blueness@g.o> wrote:
4 >> Not exactly. The point is to *standardize* what is meant by "all
5 >> information" so that all package managers export the same minimum set
6 >> of information. The most important being NEEDED.ELF.2 which is
7 >> portage's VDB but not paludis. Also, it can be in any format and
8 >> exported in any way so long as it is well documented. The goal is to
9 >> have tools other than PM's make use of this information. The example
10 >> that began this is revdep-pax which uses NEEDED.ELF.2 to trace out
11 >> linking so as to migrate PaX flags between ELF objects.
12 > VDB is completely non-standard, undocumented, and hard to read
13 > correctly. There's no point in having information if you aren't allowed
14 > to use it.
15 >
16
17 VDB as exported by portage is readable and useful to non-PM tools. I'd
18 give you a link to git.gentoo.org/proj/elfix as a concrete example, but
19 the site is still down. This usefulness suggests that it should be
20 standardize and documented so that VDB information can be read correctly
21 by non-PM tools.
22
23 --
24 Anthony G. Basile, Ph.D.
25 Gentoo Linux Developer [Hardened]
26 E-Mail : blueness@g.o
27 GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
28 GnuPG ID : F52D4BBA

Replies