Re: [PATCH] Add a "make rpmball" target

[George Dunlap <george.dunlap@eu.citrix.com>]

On 03/03/2014 04:34 PM, George Dunlap wrote:
> On 03/03/2014 04:23 PM, Olaf Hering wrote:
>> On Mon, Mar 03, George Dunlap wrote:
>>
>>
>>> +%install
>>> +rm -rf \$RPM_BUILD_ROOT
>>> +mkdir -p \$RPM_BUILD_ROOT
>> Newer rpms are supposed to do that automatically, but I dont know what
>> "newer" actually means. And certainly it does not hurt to keep this.
>>
>>> +cd %{_xenroot}
>>> +dist/install.sh \$RPM_BUILD_ROOT/
>>> +
>>> +cd \$RPM_BUILD_ROOT
>>> +
>>> +# Don't include xen-syms
>>> +rm -f boot/xen-syms*
>>> +# Remove all the "linked" xen-*.gz files
>>> +rm -f \$(find boot/ -type l)
>> "find $paht -type l -delete"?
>
> Ack.
>
>>
>>> +%files
>>> +%defattr(-,root,root,-)
>>> +/*
>> In this case, to avoid package conflicts, add some tags like:
>>
>> Obsoletes: xen-libs
>> Obsoletes: xen-tools
>
> What exactly would this be for?

"remove another named package(s) when this package is installed" -- I 
think that's a bit more than we want in the rpmball.  I'd much rather 
the developer have to remove the conflicting packages themselves, rather 
than have it done automatically.

  -George