Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#8543 - Add ability to have multiple versions of the same package installed at the same time

Attached to Project: Pacman
Opened by Mildred (mildred) - Wednesday, 07 November 2007, 01:35 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 09 November 2007, 17:55 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 3.0.6
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi,

I saw a feature in portage, the gentoo package manager, that I think could be interresting to have. They call it slots, and it is the ability they have to install multiple versions of the same package at the same time. There are many uses for that, for example to install multiple versions of the same kernel (to make shure you don't lose the materiel support with an upgrade), or even multiple versions of the same library.

Recently I was interrested in a package, openscenegraph, and there are two major versions that are very different. If a package need the version 1, the version 2 would not do. What are our possibilities now ? We can create two package, called openscenegraph and openscenegraph2. But then, do we have to do it on all the packages on the system ? How do we know when we upgrade a package if we should change its name or not ?

A better solution (from my point of view) would be to add a variable in pkgbuild that would tell if two versions of the package can be installed at the same time or not. It could take 3 values :
- 'no' : two versions mustn't be installed at the same time
- 'yes': two versions (or more) can be installed at the same time. There must not be file conflicts
- 'latest': two versions can be installed at the same time. If there is file conflicts, the file from the latest package is kept.

You could argue it is not simple enough for ArchLinux but I would answer that it is not very complicated (at least from the user point of view). Moreover, if we simplifies too much, we end up with a system that is too simple and can't handle some situations shat should be handled.

This is just an idea, and I might one day come with a patch. i hope it would be accepted then. Thanks.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Friday, 09 November 2007, 17:55 GMT
Reason for closing:  Deferred
Additional comments about closing:  Won't implement until an elegant solution is provided
Comment by Aaron Griffin (phrakture) - Thursday, 08 November 2007, 17:18 GMT
I don't think we ever want to do this. Not only does Arch explicitly NOT support multiple versions of packages, but this would also cause all sorts of management headaches.

I personally think the foobar and foobar2 package naming solution is very elegant considering this won't happen all that often.
Comment by Roman Kyrylych (Romashka) - Friday, 09 November 2007, 09:28 GMT
I agree with Aaron that it adds unnecessary headaches.
Comment by Dan McGee (toofishes) - Friday, 09 November 2007, 15:12 GMT
This won't be a straightforward change from the *developer* point of view. For now, I'd say we can close this as a "won't implement", unless someone provides a really viable and elegant solution.

Loading...