-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/15/15 10:08 AM, Mike Frysinger wrote: > On 15 Dec 2015 15:33, Michał Górny wrote: >> On Tue, 15 Dec 2015 09:19:36 -0500 Mike Frysinger wrote: >>> On 15 Dec 2015 07:28, Ulrich Mueller wrote: >>>>>>>>> On Tue, 15 Dec 2015, Mike Frysinger wrote: >>>> >>>>> On 14 Dec 2015 21:22, Ulrich Mueller wrote: >>>>>> The spec seems incomplete. I cannot find a description of the user and >>>>>> group files' format. (But in fact, there is a standard format which >>>>>> suggests itself, namely that of the passwd(5) and group(5) files.) >>>> >>>>> i recall going with xml at the time, but i can't find reference to it. >>>> >>>> So the package manager would have to parse XML? We have tried to avoid >>>> that, so far. >>> >>> not entirely accurate considering we have metadata.xml >> >> Not entirely accurate considering the contents of metadata.xml are not >> necessary to build and install packages. > > read the context. your statement is fairly obvious. > -mike i looked through portage code and we do have xml parsing sprinkled throughout, mostly in repoman for obvious reasons. why are we trying to avoid xml? to be honest i don't have strong feelings about either the flat file (a la /etc/passwd) or xml.
i'm interested in this because the hardened-sources kernel does make use of some special uid/gids. gengor pointed me to glep 27 and suggested that i implement it but i wasn't that interested. still, it would clean up the hardened. - -- 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 -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iEYEARECAAYFAlZwMJkACgkQl5yvQNBFVTV07gCdHOlrLeoLOdwbEDTeN9TlTM1m to8AoItHHwBbBvZDp1JkJw9ZO6sm6Sr3 =hYwF -----END PGP SIGNATURE-----
