Now what you might want to do is somehow unifying this task inside the scriptlets.

Now what you might want to do is somehow unifying this task inside the scriptlets.

If that's the case, please add your proposal with the two functions there :

If that's the case, please add your proposal with the two functions there :

−

[http://bugs.archlinux.org/task/10375 FS#10375]

+

[https://bugs.archlinux.org/task/10375 FS#10375]

and maybe edit the wiki accordingly.

and maybe edit the wiki accordingly.

--[[User:Shining|shining]] 04:42, 19 May 2008 (EDT)

--[[User:Shining|shining]] 04:42, 19 May 2008 (EDT)

Line 29:

Line 29:

== gdm group? ==

== gdm group? ==

−

It seems gdm creates a group when installing as well. There's a bug against its current behaviour ([http://bugs.archlinux.org/task/13690 bug 13690]), I really think it should have a group with the same gid as its uid (120).

+

It seems gdm creates a group when installing as well. There's a bug against its current behaviour ([https://bugs.archlinux.org/task/13690 bug 13690]), I really think it should have a group with the same gid as its uid (120).

== policykit is incomplete ==

== policykit is incomplete ==

Line 41:

Line 41:

== system-tools-backends ==

== system-tools-backends ==

−

This package creates a user-level group, there's a bug open for this issue ([http://bugs.archlinux.org/task/14787 bug 14787]).

+

This package creates a user-level group, there's a bug open for this issue ([https://bugs.archlinux.org/task/14787 bug 14787]).

As I started discussing it at [[Talk:Arch_Packaging_Standards#Adding_system_users]], it would be good to have a clearer process for the addition of system users, and maybe a specific sub-namespace (_e.g._ from 500 to 749) for AUR, as well as some authoritative list to avoid collisions ? Maybe another namespace (750-999?) should also be kept strictly reserved for local uses, so admins can create groups knowing that no upstream ArchLinux package will ever use the ID.

:As you can see, this discussion page doesn't get many replies from developers, you may want to use the forum or the mailing lists for this kind of requests. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 09:54, 17 June 2012 (UTC)

+

+

== oml2 entries ==

+

+

Please add oml2 user and group (both 137, arbitrarily, on a Debian system I have at hand). I'm updating the package at https://aur.archlinux.org /packages.php?ID=60321 and https://aur.archlinux.org/packages.php?ID=60322, creating these in the post_install script.

Revision as of 07:11, 28 April 2013

Why should user and group be created at build time? This sounds really weird to me.
Arch packages aren't supposed to be shared? You can very well build a package and not install it immediately.

In any cases, I think this task definitively needs to be made at install time.
That is why it is always done in scriptlets.
Now what you might want to do is somehow unifying this task inside the scriptlets.
If that's the case, please add your proposal with the two functions there :
FS#10375
and maybe edit the wiki accordingly.
--shining 04:42, 19 May 2008 (EDT)

Ossec

What about packages from AUR?

As I started discussing it at Talk:Arch_Packaging_Standards#Adding_system_users, it would be good to have a clearer process for the addition of system users, and maybe a specific sub-namespace (_e.g._ from 500 to 749) for AUR, as well as some authoritative list to avoid collisions ? Maybe another namespace (750-999?) should also be kept strictly reserved for local uses, so admins can create groups knowing that no upstream ArchLinux package will ever use the ID.