On 08/31/14 08:26, Ciaran McCreesh wrote:
On Sat, 30 Aug 2014 16:02:51 -0400
"Anthony G. Basile" <bluen...@gentoo.org> wrote:
I've written a GLEP which outlines a standard for what information
should be stored by any package management systems (PMS)
in /var/db/pkg (VDB) and mandates some API for exporting it to other
tools [1].
The problem isn't what the information is. It's the format.
That's not the point, the point is specifying what information should be
cached and exported. NEEDED.ELF.2 is cached by portage but not
paludis. Developers writing tools that make use of a PM's VDB should
know what they can expect from VDB and how to get at it. You can use any
format you like (plain ascii or some db format) as long as its
exportable to other tools.
The need to do so was discussed in the Council during the
20130910 meeting [2]. During that meeting, the council focused on
NEEDED.ELF.2 which is recorded by portage, but not paludis. Linkage
information is generated during package builds, is expensive to
recalculate and is needed by other packages like revdep-pax for PaX
marking ELF objects.
This isn't relevant to ebuilds.
The point is that developers writing tools that make use of a PM's VDB
should now what's there. A quote from the council minutes: "The council
discussed if the contents of the VDB should be specified for
interoperability between utilities, ..."
I've aimed to make the GLEP open to how each PMS team wants to
implement this without being too vague. We should also consider
carefully the list of items we want cached although we could always
update this list later.
This isn't a specification...
Correct. How you implement this is up to you to make your life as easy
as possible. What is specified in the GLEP is what information should
be cached and that a clearly documented API be produced.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : bluen...@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
