On Thu, May 02, 2002, Lars Kellogg-Stedman wrote:
> >> If I want two simultaneously installed versions of Perl, how
> >> do I handle that?
> >For this you require a second OpenPKG instance, because RPM allows only a
> >package to be installed once per instance.
>
> RPM will happily allow you to install two versions of the same package
> side-by-side, provided that there are no file conflicts. For example:
>
> $ rpm -q kernel
> kernel-2.4.7-10
> kernel-2.4.9-21
> kernel-2.4.9-31
>
> This will, of course, generally require planning on the part of the
> packager -- binaries can't be named something like "perl", instead they
> need to be named something like "perl561", with postinstall scripts that
> take of creating an appropriate symlink.
Hmmm... very interesting, I was not aware that RPM is able to do this.
I not even know what installation command I had to use to achieve this
effect. A simple "rpm -i" should leads to an error and "rpm -U" should
replace/upgrade the package. What RPM command line does RedHat use to
achieve the above situation? Even a glance over there up2date script did
not gave me any clue about this (except that they generally treat the
"kernel" package very differerent all over their up2date code).
OTOH, even with this feature, is this really appropriate for packages
like "perl"? I mean for the kernel it is clear that it is interesting
and useful, but if we would do this for "perl" we also had to do it for
really all packages to be consistent. Because this time people ask for
multiple installations of "perl", next for multiple installations of a
different package. And adding such support to all packages quickly can
become a nightmare, I think. So, where is the demarcation line here?
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
