On Mon, 2006-10-02 at 22:58 -0400, Mike Kelly wrote: > I have a list of all packages in the tree that currently use either of > those functions[2]. If you maintain one of these packages, I'd > especially appreciate your feedback.
You missed games-* (yes, all of them) via the games.eclass, but I'm sure there's a couple more eclasses that do user/group modification. > Summarized, the format is: > > For each profile dir (e.g. profiles/base, profiles/default-linux, etc), > a new subdirectory, called accounts is created as necessary. Inside > that is a file called defaults, containing default uid/gid ranges, > shells, etc for the given profile. Also, there are two directories, > user/ and group/, which contain files named after the users and groups > to be added. Those files contain more specific uid/gid info, etc. > > All the files are handled like other files in cascading profiles. Each > line in the file is either a shell-style comment, or of the form: > "key: value". The keys are: uid, shell, home, groups, comment, and gid. What about applications that aren't tied to a profile? How do they work? Doesn't this increase the size of the profiles pretty dramatically? Does it need to be tons and tons of small files, or can we get away with a set of larger files with some sort of header? eg. $ cat defaults [default] uid: 1-999 shell: /bin/false home: /dev/null groups: comment: user created by portage gid: 1-999 $ cat accounts [portage] uid: 250 shell: /bin/false home: /var/tmp/portage groups: portage comment: portage gid: 250 [apache] uid: 81 shell: /bin/false home: /var/www/localhost groups: apache comment: apache gid: 81 As you can see, this changes very little, but reduces the number of small files in the portage tree. Is this necessary? Who knows? Will it makes syncs slightly faster? Not a clue. I'm just throwing out an idea. Anyway, this looks really good. =] -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation
signature.asc
Description: This is a digitally signed message part
