Of course, if OpenPKG were using the depot conventions, as outlined in our Dec. 2001 LISA paper on merging RPM and depot, you could have as many versions of perl as you like living in parallel with one another (even in the case of file name conflicts), and in addition be able to (optionally) share these packages over a network from a central server. Michael Schloh von Bennewitz of the OpenPKG developers group wrote a nice reply some days back to my proposal to merge OpenPKG and depot, and I will get back to him shortly with a proposal about how we might do that in a gradual manner. I really think this could add much to the value of OpenPKG, which could and should become the universal open source model for software package management.
Cheerio, Rick Rodgers > From [EMAIL PROTECTED] Thu May 2 13:01:41 2002 > From: Lars Kellogg-Stedman <[EMAIL PROTECTED]> > Subject: Re: How does OpenPKG undo? How does OpenPKG handle multiple versions? > > >> 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. > > -- Lars ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
