On Tue, 2007-02-27 at 10:41 -0500, Matt Hyclak wrote:
> On Tue, Feb 27, 2007 at 12:19:41PM -0300, Dago Pacheco enlightened us:
> > i'm kinda newbie in centos.... so clear me something... you say that I
> > must put this entry
> >
> > #released i386 updates
> > [update-i386]
> > name=CentOS-$releasever - i386 Updates
> > mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=i386&repo=updates
> > #baseurl=http://mirror.centos.org/centos/$releasever/updates/i386/
> > gpgcheck=1
> > gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4
> > enabled=0
> > protect=1
> >
> >
> > in /etc/yum.repos.d/CentOS-Base.repo , right?
> > is there anything else that i must consider?
> >
>
> I would put it in a separate file, e.g. firefox-i386.repo so that it isn't
> overwritten with upgrades to the package that owns CentOS-Base.repo.
> Otherwise, that's all you should need.
Good idea to put it in another file as it may be less confusing, but it
should not be necessary to keep it from getting overwritten by an
upgrade, which should create CentOS-Base.repo.rpmnew if the file has
been modified. Either putting it in CentOS-Base.repo or in a new file
will have the same effect.
The new file, if used, can be called anything with a .repo extension as
long as it lives in /etc/yum.repos.d/ - but it helps if the name is
something related to the contents. My suggestion would be
"update-i386.repo" for the example I gave, as that will clue you in as
to what the parameter to "yum --enable <repo> ..." should be.
Another consideration might be to avoid doing something like "yum
--enable update-i386 update" as you might get more than you bargained
for in the way of new i386 packages.
Phil
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
