1 |
On Tue, 03 Oct 2006 08:09:08 -0400 |
2 |
Chris Gianelloni <wolf31o2@g.o> wrote: |
3 |
|
4 |
> > I have a list of all packages in the tree that currently use either |
5 |
> > of those functions[2]. If you maintain one of these packages, I'd |
6 |
> > especially appreciate your feedback. |
7 |
> |
8 |
> You missed games-* (yes, all of them) via the games.eclass, but I'm |
9 |
> sure there's a couple more eclasses that do user/group modification. |
10 |
|
11 |
Oops, I forgot to account for eclasses. I'll redo my script and run it |
12 |
again later to account for that. |
13 |
|
14 |
> What about applications that aren't tied to a profile? How do they |
15 |
> work? |
16 |
|
17 |
Well, user management is inherently tied to the userland which is being |
18 |
used, which is in turn tied to the profiles (default-linux, |
19 |
default-bsd, etc). |
20 |
|
21 |
Settings which are userland-agnostic (like default uids, member groups, |
22 |
GECOS comment fields), would be in the settings for the base/ profile. |
23 |
|
24 |
> Doesn't this increase the size of the profiles pretty |
25 |
> dramatically? |
26 |
|
27 |
I don't think it makes that much of a size difference. Most of this |
28 |
information is now duplicated over many enewuser/group lines in many |
29 |
different ebuilds. With this system, ebuilds just need to have a EUSERS |
30 |
and EGROUPS variable defined listing the users/groups needed. |
31 |
|
32 |
> Does it need to be tons and tons of small files, or can |
33 |
> we get away with a set of larger files with some sort of header? |
34 |
> |
35 |
> As you can see, this changes very little, but reduces the number of |
36 |
> small files in the portage tree. Is this necessary? Who knows? Will |
37 |
> it makes syncs slightly faster? Not a clue. I'm just throwing out an |
38 |
> idea. |
39 |
|
40 |
Hmm, parsing that would be a more difficult task for my scripts (which |
41 |
are just basic bash code doing some greps). Also, it seems like the many |
42 |
small files are easier to maintain. I don't know enough about rsync to |
43 |
know how it would affect efficiency, though. It's something I'll try |
44 |
and look into further. |
45 |
|
46 |
> Anyway, this looks really good. =] |
47 |
|
48 |
Thanks! |
49 |
|
50 |
-- |
51 |
Mike Kelly |