-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/15/15 4:55 PM, Mike Frysinger wrote: > On 15 Dec 2015 22:35, Ulrich Mueller wrote: >> Whatever the format will be, the more important question is where this >> would be implemented: >> >> - In the package manager, with user and group definition in profiles. >> This seems to be what GLEP 27 suggests, and as far as I can see, it >> would require an EAPI bump. Certainly doable, but last time we >> bumped profiles to a new EAPI we had a rather long transition >> period. >> >> - In user.eclass, which could be extended to use the EUSERS and >> EGROUPS variables defined in ebuilds. The problem is, where would >> one store the user and group definitions then? Profiles cannot be >> accessed from an eclass. > > long term, i think profiles are better to hold the db as it provides for > clean stacking and is trivial for site-specific extension/control, as well > as image builders via something like catalyst. > > short/mid term, i was thinking of writing a new package that holds the db > and tools to query/manage it. user.eclass would DEPEND on it and ask it > for details, perhaps even doing the actual fs updates (the bash code here > is not pretty wrt locks and python would be much nicer). that tool could > even search additional site paths (like /usr/local) to locate overrides.
how do we get our own uid/gid's in there for our packages? just open a bug against the new package? > > > the API to ebuilds/eclasses would be unchanged. in CrOS, we only look at > the first argument (the user/group name) and load all other details from > the db. we could seamlessly migrate over existing ebuilds by opting in to > this simpler form. > > maybe the short/mid term solution is enough to not get into profile mess > even if i think it's the correct data storage location. > -mike - -- Anthony G. Basile, Ph.D. Gentoo Linux Developer [Hardened] E-Mail : [email protected] GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA GnuPG ID : F52D4BBA -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iEYEARECAAYFAlZwvQcACgkQl5yvQNBFVTVEaACfT1nMMFXsPyqM0u4rGDHJP29/ pFkAn0XOcHTmVAAp9K9opvWT9isuMOxp =xPUD -----END PGP SIGNATURE-----
