Re: multiarch status update
"Olaf van der Spek" <firstname.lastname@example.org> writes:
> On 5/14/06, Martijn van Oosterhout <email@example.com> wrote:
>> both versions installed, or deal with it via alternatives. They should
>> be indistinguishable from a users point of view.
> 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?
How should the depends decide when that is needed or wanted and when
not? Esspecialy when different versions are available per
How would programs or user specifiy what binary to call? How would
users even know which binary is which if they have the same name and
both packages are installed on the system? Just imagine the confusion
of a user installing foo (which provides the same binary "foo" as bar)
and calling foo gives him bars "foo".
That is totaly out of the question. Packages that provide the same (by
name) binary (or even just file) MUST conflict. period.