Re: Building rpms in mock

Sam Varshavchik writes:

> I think that right now it's more important to put in safeguards to prevent  
> updating to an incompatible newer version that was accidentally built with a  
> different user or group id. I have some ideas on how to make that happen.  
> I'm going to try the following:
>
> Explicitly define mailuser and mailgroup in the spec file, as defines, and  
> they can be overriden. The mailuser and mailgroup defines get passed through  
> as the corresponding options to configure.
>
> An additional define, passed through to configure, to be used as a dumping  
> ground for all other options.
>
> A courier-authlib-config-%{mailuser}-%{mailgroup} empty subpackage. So,  
> it'll be courier-authlib-config-daemon-daemon for me, and courier-authlib- 
> config-courier-courier for you. The name is ugly, but who cares. Both  
> courier-authlib, and all other packages will get a dependency on this  
> subpackage. I think this can be done in a way that'll work even for the old  
> version of rpm in centos 7.

I tried this, and this works reasonably well. The default "courier-authlib- 
config-daemon-daemon" subpackage looks like an odd duck, but that's what it  
takes to make an omelette. I tried building courier-authlib configured with  
a different userid, throwing the end results into a repository. dnf detected  
a dependency resolution failure and refused to proceed. The dependency  
resolution failure looks like another odd duck, but it does the job.

The courier-authlib, courier, courier-imap, and sqwebmail packages' spec  
files were updated with the new dependency scheme.



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