On Sun, May 14, 2006 at 01:19:14AM +0200, Tollef Fog Heen wrote: > Henning Makholm wrote: > > >In multiarch, the right approach to this particular problem is to > >arrange for /usr/bin/python to be a symlink to /usr/bin/$arch/python > >with $arch chosen (somehow) appropriately for a default python > >interpreter. > > Apart from the fact that no multiarch proposals have tried to > multiarchify /usr/bin and /bin, but are rather letting applications for
Some multiarch proposals provided non-conflicting path for executables as well. What they failed to do was to allow to install two packages containing the same executable for two different plateforms. > which multiarch makes sense (think gcc) handle this themselves. How ? > I so far haven't seen any compelling arguments for multiarchifying the > whole archive including all of */bin. Personnally I would favor a new files hierachy that allow every arch-dependend files to be co-installable. Even if we are not able to take full advantage of it at once, it seems saner and more forward-looking than only allowing libraries to be co-installable. This might also make easier to have this new scheme adopted by other OS. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
