Subject: Re: PLIST content
To: None <firstname.lastname@example.org>
From: None <email@example.com>
Date: 07/02/2006 22:43:22
On Sun, Jul 02, 2006 at 10:31:36PM +0200, Hubert Feyrer wrote:
> On Sun, 2 Jul 2006 firstname.lastname@example.org wrote:
> >(1) Normal files
> >- path name relative to PREFIX
> >- file content is associated (e.g. in the binary package or the file
> >- meta data consists of:
> > * owner, group, permissions
> > * checksums (algorithm, value pairs, default SHA1 and RMD160)
> > * modification time
> > * optionally triggers
> Is the metadata kept/maintained in the PLIST file too, or is it kept
> elsewhere (hopefully automatically)?
> Also: Reading this makes me thing "mtree".
Yes, the format it will end up is most likely *similiar* to mtree. I
consider the mtree input partly brain-damaged, but that's unrelated.
One problem with mtree is that it is too powerful for the pkgsrc use.
Most of the information are supposed to be automatically added to the
PLIST of the pkgsrc description. I do expect that we want to allow
manual specification e.g. for ownership. We talked about this on
pkgsrccon (normalisation of permission and ownership as part of staged
The full list is stored in a binary package or the pkgdb, but it is not
part of this proposal how. In fact, depending on the "format" the
encoding can be different, since e.g. a tarball can store them