On Fri, 12 Oct 2012, Hemberly, Paraszt wrote:
So after a fresh Scientific Linux 6.3 Desktop install, I:
yum install rpmforge-release && yum update
and
yum install epel-release.noarch
then:
yum install wine gparted cups-pdf && echo 'includepkgs=nss-mdns wine*
gparted cups-pdf' >> /etc/yum.repos.d/epel.repo
OK! After this I:
vi /etc/yum.repos.d/epel.repo
includepkgs=nss-mdns wine* gparted cups-pdf
So this is how I install a fresh wine (+cups-pdf) and gparted.
*Q*: Is this a stable thing to do? I mean can this cause problems in the
future? (that there are some epel packages installed, but I use a whitelist
after installing the mentioned few packages to help stability - because I
only need epel for the few things gparted/wine/cups-pdf). Will these stepes
cause problems in the future?
I've had problems when mixing epel and rpmforge on an SL5 machine
when a package depends upon a package which exists in both repos
but with different numbering or features (sometimes one split the
package into several sub-packages).
My impression is that in SL6 rpmforge has dropped many of the
duplicated packages, perhaps because they are already in Fedora.
My advice would be to install rpmforge-release and epel-release
but to edit /etc/yum.repos.d/rpmforge.repo and
/etc/yum.repos.d/epel.repo so that they say enabled=0 for every repo
and explicitly enable that repo when you wish to install a package
from either, then you can at least see what is going on.
That does mean you wont automatically get updates for these repos
so you should run
yum --enablerepo="*" check-update
from time to time (overnight cron job ?).
--
Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge
[email protected] http://www.dpmms.cam.ac.uk/~werdna
