forked from kiss-community/repo
Determine how to handle user/group creation #13
Labels
No Label
core
extra
help wanted
new package
question
update
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: bonsai/repo#13
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
openntpd (introduced in
bd5572eef5
) automatically creates a user and group upon installation if needed:The user and group is not removed with the package, and an informational message is printed to the console upon removal.
Good enough? Or should more or less be done?
FWIW, kiss-community/community repo does not create the user for their openntpd package and instead asks the user to do so themself.
I think auto-creating and notifying on removal is good enough.
I personally would prefer letting the user create the group so they can configure the system to their liking if they wish the setup to be different.
if we do prompt to create a user & group then we should specify what the default is. my main concern is that someone would set & forget a name for it and then while seeking support it adds an extra step of complication.
I would prefer to have one default style for the reasons you mention but I know often distributions have made users/groups for me with silly names. I can't think of an example off the top of my head but I know I had to patch android-udev-rules to make it use
wheel
for adb access and not the perhaps more descriptive but in my mind unnecessary additional groupadbusers
.It would be easier to follow in the footsteps of kiss-community. I haven’t taken a look to see if this is exactly how they handle it, but i think we should specify a default and let the user leave the name empty if they want to keep the default.