Re: multiarch status update
On 5/15/06, Goswin von Brederlow <email@example.com> wrote:
> Being able to install multiple versions is some use to multiarch, but
> could also be used for other things, such if two packages provide the
> same binary (git for example).
> Or to install multiple 'version 'numbers' of the same package.
The big problem then is when to install multiple versions of a binary?
When a dependency or user asks for it explicitly for example.
How should the depends decide when that is needed or wanted and when
not? Esspecialy when different versions are available per
That depends on the implementation but I don't think it's not solvable.
How would programs or user specifiy what binary to call? How would
A program would do it via dependency and configuration information.
A user would (for example) do it via configuration.
users even know which binary is which if they have the same name and
both packages are installed on the system?
A user could use the full path or 'symlink' the full path to a unique
name. Instead of symlinks another more flexible approach could also be
Just imagine the confusion
of a user installing foo (which provides the same binary "foo" as bar)
and calling foo gives him bars "foo".
Should I imagine that the user has installed bar?