I was wondering how practical it would be to install a RPM Package in the same way that a Source Program is Installed. I'm looking for a work around, around CentOS/Scientific Repo Conflicts. Is there a framework for this already in existence?

Thanks in advance!

Are you using yum-priorities? You can get advice about using multiple repositories at
http://wiki.centos.org/AdditionalResources/Repositories
You can also protect a particular package by adding 'exclude=program_name' to /etc/yum.conf.

I've got CentOS, RPMforge, and EPEL all active. I've also installed RPMs from fedora and Mandriva.

1 members found this post helpful.

Which rpm package is this about ? ?
And where do you want the files installed ?

1) This command will allow you to install an extra version
of a library : # rpm -ivh <package.rpm>

If unimportant files ( man pages, documentation )
are conflicting : # rpm -ivh --force <package.rpm>


2) This command will unpack any package to a new directory,
e.g. /usr/local/<?>/ :
cd /usr/local/<?>/ ; su ; rpm2cpio <package.rpm> | cpio -idmv

If it's a package containing an executable (or a 'start script'),
the file can be symlinked to /usr/local/bin/ : It's in the PATH.

.

1 members found this post helpful.

I'm only up to speed on this to ask further questions but this in not too far out of reach.

This is the standard Install command with Verbose and Hatching so it must be a typo correct?

I'm curious as to the background necessary to do this. How are you able to use Mandriva RPMs and how are the wrong "everything" versions, etcetera accepted by yum?

Basically I was thinking that If more than one Version of RPM was installed it would take care of the Conflicts by doing some of the Installations using non shared Libraries, or partially anyways. A Redhat Package Manager for each Repo but only NOT share the cause of major conflicts to keep the Data Base smaller. Most libraries would be shared. If I have some of the real problematic Libraries being independent of RPM they would be installed outside of RPM.

I'm not currently able do implement this but I was thinking of a smaller manual method.


I don't have a specific Package issue I'm just trying to do things More organized on a new CentOS install. I had a CentOS 6 meltdown by it's own updates but 6 and not 6.1 is the only game it town if you want packages. I have Scientific installed but it's 6.1 and not a thing is available for it yet.


I have Rollback of updates configured ,and I installed yum-plugin-priorities- yum-plugin-protectbase installed.

# 4.
No. The standard command is 'rpm -Uvh' : used by yum and Package Managers.

'rpm -ivh <name>' is for the exceptions only.
Can be used if you are absolutely sure that no package with <name>
is installed. Or for an extra version, usually a library.
.

1 members found this post helpful.

what packages are causing the problem
it is almost certainly a issue that can be solved with the correct settings for yum-priorities

or with a specific "exclude=" option

some repos ARE INCOMPATIBLE with others
some are only some what incompatible
so will KILL an install

now 6 is WAY better than 5 BUT there are still some issues
so heed ALL warnings on the cent wiki ( applies to SL also )
http://wiki.centos.org/AdditionalResources/Repositories
and as i recall with SL6 there is an EXTRA WARNING
rmpforge IS FINE BUT rpmforge-extras is INCOMPATIBLE with upstream rhel6 / sl 6


it is still a bit of a mine field so pay VERY CLOSE attention to the "yum-priorities " settings
just what you set to 99 or 90 or 80 or 70 ... is VERY important


having and using multiple repos on cent6/sl6/rhel6 can make setting up "yum-priorities " very hard
and there will be A LOT of trial and error
i currently have something like 1,700 rpms blocked do to the settings
just so that they will NOT mess up the install

I do not want rpmforge to replace some things nor do i want epel to replace some things

1 members found this post helpful.

John's right: this is a 'black art'. When I first installed CentOS 6.2, I could not get Claws-mail to install. I finally discovered that RPMforge was blocking a dependency in EPEL, so I just had to switch the priorities so that EPEL was 2 and RPMforge 3. Another trick is to disable whichever of the two extra repos you're not using for a particular program.

As for using stuff from other distros, CentOS actually recommend that so that as much as possible is in the rpm database. Installing with yum will pull in any necessary dependencies. In the case of the Wine rpm from Mandriva, yum couldn't find xmessage, but it was easy to discover the CentOS package that provided it.