On Friday 23 March 2007, Chris Jones wrote: > On Friday 23 March 2007 5:35:58 pm Ed Greshko wrote: > > Kevin Kofler wrote: > > >>> In which case you set up yum to *only* take firefox from Remi's repo, > > >>> and nothing else. Problem solved. > > >> > > >> Right, sure, yes.....explain that to the clueless. > > > > > > su - > > > rpm -Uvh \ > > > http://remi.collet.free.fr/rpms/fc6.i386/remi-release-1-2.fc6.remi.noar > > >ch .rpm head -n 7 /etc/yum.repos.d/remi.repo > > > >/etc/yum.repos.d/remi.repo.new sed -i -e 's/enabled=[01]/enabled=1/g' > > > /etc/yum.repos.d/remi.repo.new echo 'includepkgs=firefox devhelp > > > epiphany galeon > > > gnome-python2-gtkmozembed '\ 'gtkmozembedmm liferea yelp' > > > > > > >>/etc/yum.repos.d/remi.repo.new > > > > > > tail -n +8 /etc/yum.repos.d/remi.repo >>/etc/yum.repos.d/remi.repo.new > > > echo 'includepkgs=firefox devhelp epiphany galeon > > > gnome-python2-gtkmozembed '\ 'gtkmozembedmm liferea yelp' > > > > > > >>/etc/yum.repos.d/remi.repo.new > > > > > > mv -f /etc/yum.repos.d/remi.repo.new /etc/yum.repos.d/remi.repo > > > > > > This should be ready for copy&paste. :-) What this does: > > > * installs remi-release > > > * copies the [remi] (not [remi-test]) part of remi.repo to > > > remi.repo.new * enables the repo > > > * adds the includepkgs directive > > > * appends the info for [remi-test], disabled by default > > > * adds the includepkgs directive there too > > > * moves the result back to remi.repo > > > > Wow....that will *really* help the clueless. > > > > You are joking, right? > > I think he was... > > Anyway, its really no where need as complicated as that. All I did was > > > rpm -Uvh > > http://remi.collet.free.fr/rpms/fc6.i386/remi-release-1-2.fc6.remi.noarch > > > yum upgrade firefox --enablerepo=remi > > and it runs fine. I didn't update the other apps (epiphany galeon etc.) as > I don't use them (or gnome in fact). Firefox 2 seems just fine without > those updates.... > If you do you might have to I guess ? > > Chris Doesn't the yum protect-base plugin help in this situation. I would have thought that installing the plugin, then adding protect=1 to the remi repo would ensure that it doesn't get overwritten by any other repo. Anne
