--- 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 @@ --> - + GLEP 27 -- Portage Management of UIDs/GIDs @@ -22,7 +22,7 @@ [Gentoo Linux Home] [GLEP Index] -[GLEP Source] +[GLEP Source]
@@ -33,9 +33,9 @@ - + - + @@ -43,52 +43,57 @@ - + - +
Title:Portage Management of UIDs/GIDs
Version:1.1
Version:1.3
Last-Modified:2004/05/29 14:31:58
Last-Modified:2004/07/20 18:19:27
Author:Mike Frysinger <vapier at gentoo.org>
Type:Standards Track
Content-Type:text/x-rst
Content-Type:text/x-rst
Created:29 May 2004
Post-History:29-May-2004
Post-History:29-May-2004, 20-Jul-2004

-

Contents

+

Contents

+
+

Status

+

This GLEP was approved as-is on 14-Jun-2004.

+
-

Abstract

+

Abstract

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.

-

Motivation

+

Motivation

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.

-

Specification

+

Specification

-

Portage Structure

+

Portage Structure

-

Defining Accounts

+

Defining Accounts

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.

-

Local Overrides

+

Local Overrides

Following the tried and true style of custom local portage files being found in /etc/portage, this new system will follow the same. Users can setup their own directory heirarchy in /etc/portage/accounts/ that mimics @@ -141,9 +146,9 @@

-

Developer Interface

+

Developer Interface

-

EUSERS + EGROUPS

+

EUSERS + EGROUPS

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.

-

Defining Accounts

+

Defining Accounts

Any developer is free to add users/groups in their ebuilds provided they create the required account definition files.

-

User Interface

+

User Interface

-

users-update

+

users-update

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).

-

FEATURES=noautoaccts

+

FEATURES=noautoaccts

This is for the people who never want portage creating accounts for them. When portage needs to add an account to the system but "noautoaccts" is in FEATURES, portage will abort with a message instructing the user to @@ -179,7 +184,7 @@

-

Rationale

+

Rationale

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.

-

Backwards Compatibility

+

Backwards Compatibility

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.

-

References

+

References

@@ -203,15 +208,15 @@
- +