/[gentoo]/xml/htdocs/proj/en/glep/glep-0027.txt
Gentoo

Diff of /xml/htdocs/proj/en/glep/glep-0027.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.1 Revision 1.4
1GLEP: 27 1GLEP: 27
2Title: Portage User Management 2Title: Portage Management of UIDs/GIDs
3Version: $Revision: 1.1 $ 3Version: $Revision: 1.4 $
4Last-Modified: $Date: 2004/05/29 14:31:58 $ 4Last-Modified: $Date: 2005/09/15 02:39:54 $
5Author: Mike Frysinger <vapier@gentoo.org> 5Author: Mike Frysinger <vapier@gentoo.org>
6Status: Draft 6Status: Draft
7Type: Standards Track 7Type: Standards Track
8Content-Type: text/x-rst 8Content-Type: text/x-rst
9Created: 29 May 2004 9Created: 29 May 2004
10Post-History: 29-May-2004 10Post-History: 29-May-2004, 20-Jul-2004
11 11
12
13Status
14======
15
16This GLEP was approved as-is on 14-Jun-2004.
12 17
13Abstract 18Abstract
14======== 19========
15 20
16The current handling of users and groups in the portage system lacks 21The current handling of users and groups in the portage system lacks
45 50
46Defining Accounts 51Defining Accounts
47''''''''''''''''' 52'''''''''''''''''
48 53
49 54
50A new directory will need to be added to the rsync tree to store the 55New directories will need to be added to the rsync tree to store the files
51files that define the default values for new accounts. 56that define the default values for new accounts. They will be stored on a
57per-profile basis, that way sub-profiles may easily override parent profiles.
58The default location will be the base profile since all other profiles inherit
59from there.
52 60
53:: 61::
54 62
55 portage/profiles/accounts/ 63 portage/profiles/base/accounts/
56 user/<username>.xml 64 user/<username>
57 group/<groupname>.xml 65 group/<groupname>
58 accounts.xml 66 accounts
59 67
60The files are named with the respective user/group name since they need 68The files are named with the respective user/group name since they need
61to be unique in their respective domains. For example, the file 69to be unique in their respective domains. For example, the file
62detailing the ntp user would be located accounts/user/ntp.xml. Each 70detailing the ntp user would be located accounts/user/ntp. Each
63username.xml file will detail the required information about each user. 71username file will detail the required information about each user.
64Certain account features that exist on one class of systems (Linux) but 72Certain account features that exist on one class of systems (Linux) but
65not on others (\*BSD) can be tagged as such. Each groupname.xml will 73not on others (\*BSD) can be redefined in their respective subprofiles. Each
66follow similar guidelines. The accounts.xml will be used to describe 74groupname will follow similar guidelines. The accounts file will be used to
67global account defaults such as the default range of 'valid system' ids. 75describe global account defaults such as the default range of 'valid system'
68For example, if the UID 123 is already used on a system, but the ntp 76ids. For example, if the UID 123 is already used on a system, but the ntp
69user defaults to '123', we obviously cannot just duplicate it. So we 77user defaults to '123', we obviously cannot just duplicate it. So we
70would select the next available UID on the system based upon the range 78would select the next available UID on the system based upon the range
71defined here. 79defined here.
72 80
73 81
74Local Overrides 82Local Overrides
75''''''''''''''' 83'''''''''''''''
76 84
77Following the tried and true style of custom local portage files being 85Following the tried and true style of custom local portage files being
78found in /etc/portage, this new system will follow the same. Users can 86found in /etc/portage, this new system will follow the same. Users can
79setup their own directory heirarchy in /etc/portage/accounts/ that mimics 87setup their own directory heirarchy in /etc/portage/profile/accounts/ that
80the heirarchy found in the portage tree. When portage attempts to add a 88mimics the heirarchy found in the portage tree. When portage attempts to add
81new user, it will first check /etc/portage/accounts/user/<username>.xml. 89a new user, it will first check /etc/portage/profile/accounts/user/<username>.
82If it does not exist, it will simply use the default definition in the 90If it does not exist, it will simply use the default definition in the
83portage tree. 91portage tree.
84 92
85 93
86Developer Interface 94Developer Interface

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.4

  ViewVC Help
Powered by ViewVC 1.1.20