On Mar 11, 2011, at 10:15, Tim Edwards wrote:
> On 11/03/11 10:05, Andreas Petzold wrote:
>> Hi,
>>
>> in SL5 I replaced the stock yum repository files and /etc/yum.conf with
>> files
>> customized for our site (local repo mirrors, special excludes etc.) with an
>> RPM with the following properties:
>>
>> Requires: redhat-release >= %{version}
>> Provides: yum-conf
>> Provides: epel-release-5
>> Obsoletes: yum-conf
>> Obsoletes: yum-conf-epel
>> Obsoletes: epel-release
>>
>> With this setup we were able to prevent updates from SL from clobbering our
>> repo setup. This worked fine, since the yum-conf package owns /etc/yum.conf
>> on
>> SL5.
>>
>> On SL6 however, yum.conf is owned by the yum package. It doesn't make sense
>> for us to rebuild that just to insert our own yum.conf. Of course, we will
>> have to change a few things to accomodate the new sl-release rpm, but that's
>> fine.
>>
>> Any ideas?
use a trigger:
%triggerin -- yum
install -m 644 /my/yum/conf /etc/yum.conf
> You're not the only one, I found this extremely irritating as we use
> puppet to manage yum config.
yum.conf is marked %config(noreplace). Once modified, updates won't overwrite
it.
In my opinion, SL does the right thing here by not deviating from RHEL
unnecessarily.
Regards,
Stephan
--
Stephan Wiesand
DESY -DV-
Platanenallee 6
15738 Zeuthen, Germany
