> I disagree about the user/group creation, at least the way it's being > planned in here. > > The way openSUSE solved this problem probably makes sense for dealing > with issues like needing the users+groups to exist before package is > being installed: > > 1. sysusers are in their own (sub)packages, dep generators generate user() > and group() Provides > 2. main package can require those user() and group() names, forcing > the sysusers to be installed first > 3. Transaction ordering deals with the rest of the problem :) Sounds like something similar debuginfo packages where we don't have to do anything besides compiling with debug symbols, except that here we'd need to either install the sysusers file if it comes from upstream or create one, and I assume everything else would be handled automatically? I would be on board for such a change, as I would like to do that for the varnish package (ideally on el7 too if that can be ported over there). I have strongly considered doing that manually since this needs to be done beforehand, and in my specific case (wearing my upstream hat) we would be fine with the user short-circuiting the sysusers file prior to installation as the users/group we recommend are optional and /usr/*bin/varnish* tools can also work with other arbitrary credentials of the sysadmin's discretion to drop privileges. (Please keep the latter in mind for other packages, they may break if someone drops a different sysusers file in /etc, but ten they probably asked for it.) Dridi _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
