--- xml/htdocs/proj/en/glep/glep-0027.html 2004/05/29 14:48:18 1.1 +++ xml/htdocs/proj/en/glep/glep-0027.html 2004/07/20 18:21:20 1.2 @@ -8,7 +8,7 @@ -->- +
|Title:||Portage Management of UIDs/GIDs|
|Author:||Mike Frysinger <vapier at gentoo.org>|
|Created:||29 May 2004|
This GLEP was approved as-is on 14-Jun-2004.+
The current handling of users and groups in the portage system lacks policy and a decent API. We need an API that is both simple for developers and end users.
Currently the policy is left up to respective ebuild maintainers to choose the username, id, shell settings, etc... and to have them added in the right place at the right time in the right way. When the @@ -103,11 +108,11 @@ change.
A new directory will need to be added to the rsync tree to store the files that define the default values for new accounts.
@@ -130,7 +135,7 @@ defined here.
Ebuilds that wish to add users or groups to the system must set these variables. They are both space delimited lists that tells portage what users/groups must be added to the system before emerging the ebuild. The @@ -152,15 +157,15 @@ are ever run.
When this script is run, all the users/groups that have been added by portage to the system will be shown along with the packages that have added said users/groups. Here they can delete accounts that are no longer @@ -169,7 +174,7 @@ owned by the account).
Developers no longer have to worry about how to properly add users/groups to systems and worry about whether or not their code will work on all systems (LDAP vs local shadow vs cross compile vs etc...). Users can @@ -188,13 +193,13 @@ accounts.
Handled in similar fashion as other portage rollouts. When using the new account system, add a DEPEND for the required version of portage to the ebuild.