Re: Building rpms in mock

> The path of least resistance is to add a single option 
> to add a single encompassing parameter:

> %configure %{?config_flags}

I started doing just that, but then encountered greater
resistance elsewhere. Consider this:

%pre
getent group courier > /dev/null || groupadd -r -g 900 courier
getent passwd courier > /dev/null || useradd -r -g courier -u 900 -d %{_exec_prefix}/lib/courier -s /sbin/nologin -c "Courier mail" courier
exit 0

and then somebody doing this:

mock --rebuild --define \
  'config_flags --with-mailuser=mailserver  --with-mailgroup=mailserver'

The result would be a mess. Hence, the user's choices of
mailgroup and mailuser need to be passed to %pre, but in
order to do that they need to be defined individually and
not as part of a random string in %{?config_flags}.

The more I think about it, the more I think it would make
a lot of sense to ask for a statically allocated uid:gid
for courier and fix the user:group to that. It would have
the benefit of all rpm installations being identical in
this respect and smoothly upgradable without breakages
such as a daemon:daemon upgrade of a courier:courier
installation or vice versa not starting because all the
certificates in /usr/lib/courier/share/ are chmod 600 to
the wrong user:group.

https://docs.fedoraproject.org/en-US/packaging-guidelines/UsersAndGroups/

Z


-- 
Слава Україні!
Путин хуйло!


_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users