Subject: | |
From: | |
Reply To: | |
Date: | Fri, 11 Mar 2011 10:48:45 +0100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Hi Stephan,
On Friday, March 11, 2011 10:34:53 Stephan Wiesand wrote:
> 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
hmm, sounds like an option. Thanks for the hint.
Cheers,
Andreas
|
|
|