Seth,
The latter. Here are a few listings of the actual RPMs, and the
header names match:
pathscale-2.3.1-0.x86_64.rpm
pathscale-2.4-0.x86_64.rpm
pathscale-2.4-ptools.x86_64.rpm
pathscale-2.5-ptools.x86_64.rpm
pathscale-3-0.ptools1.x86_64.rpm
pgi-5.2-4.x86_64.rpm
pgi-6.1-3.ptools2.x86_64.rpm
pgi-6.1-3.x86_64.rpm
pgi-6.1-5.ptools.x86_64.rpm
pgi-6.1-5.x86_64.rpm
pgi-6.2-4.ptools2.x86_64.rpm
pgi-6.2-4.ptools.x86_64.rpm
I have to honestly say that I haven't tried it, but I have had
dependency errors with a few other locally built packages conflicting
with FC provided versions with the same name (subversion comes to
mind), and we had to change the names.
DO I need to use the installonly plugin/directive?
Thanks for your help.
On TuesdayMay 1, 2007, at 10:14 PM, seth vidal wrote:
On Tue, 2007-05-01 at 20:35 -0600, Wayne Sweatt wrote:
If I have 4 or 5 versions of say pgi or intel compilers that I
need to
make available on a compile server, and each version installs into
it's
own directory tree, such as /opt/PGI/6.7.8 & /opt/PGI/6.7.9 , etc...
then can yum do this? Will it complain and/or try to upgrade?
Would I use installonly?
How do I do this?
There would be no conflict per se, and I've been doing this with
rpm, and
wish to move to yum.
How are the pkgs named? Are they named:
pgi679-6.7.9-1
or are they named:
pgi-6.7.9-1
pgi-6.7.8-1
or something like that
in either case there is a way to make them work, provided you're not
installing them with rpm --force or any such silliness.
-sv
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxxxxx
https://lists.dulug.duke.edu/mailman/listinfo/yum
