Re: multiarch status update
Scripsit "Olaf van der Spek" <email@example.com>
> Goswin von Brederlow <firstname.lastname@example.org> wrote:
>> That would be total insanity. Just think about the number of scripts
>> with "#!/usr/bin/python" in it that would have to be changed. And how
> Shouldn't such hard-coded paths be avoided in the long term (anyway)?
The Linux kernel requires a full path for #! scripts. This makes
sense if one considers a #! program to be something that should have
predictable behavior no matter what the user happens to have in his
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
Henning Makholm "Detta, sade de, vore rena sanningen;
ty de kunde tala sanning lika väl som någon
annan, när de bara visste vad det tjänade til."