Re: multiarch status update
On 5/13/06, Henning Makholm <firstname.lastname@example.org> wrote:
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
One option would be to improve the Linux kernel. :)
Another option would be to update the #! line at install time with the
sense if one considers a #! program to be something that should have
predictable behavior no matter what the user happens to have in his
If the independence is a requirement, yes.
But I don't think it has to be a requirement.
And I think you can replace the path way with a better solution.
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
Such symlinks don't seem to be very flexible, as they're basically system wide.