On Oct 29, 2003, at 7:39 PM, David R. Morrison wrote:
My guess is that what happens is this: the configure script for some
package runs which perl and then uses the answer to decide what to
write in the perl scripts for that package. dpkg must be one of the
things affected by this.
Sure _
On Oct 29, 2003, at 6:22 PM, jfm wrote:
/sw/sbin/install-info: /sw/bin/perl: bad interpreter: No such file or
directory
/sw/sbin/update-alternatives: /sw/bin/perl: bad interpreter: No such
file or directory
~# grep '/sw/bin/perl' /sw/sbin/install-info
/sw/sbin/update-alternatives
On Wed, Oct 29, 2003 at 01:39:39PM -0500, David R. Morrison wrote:
My guess is that what happens is this: the configure script for some
package runs which perl and then uses the answer to decide what to
write in the perl scripts for that package. dpkg must be one of the
things affected by
Shouldn't system-perl simply put in a /usr/bin/perl - /sw/bin/perl symlink?
That seems much easier.
Unfortunately, that runs contrary to fink's policy of not modifying /usr
but confining itself to /sw (with the sole exception of a fink-installed
xfree86).
-- Dave
On Wed, Oct 29, 2003 at 04:30:32PM -0500, David R. Morrison wrote:
Shouldn't system-perl simply put in a /usr/bin/perl - /sw/bin/perl symlink?
That seems much easier.
Unfortunately, that runs contrary to fink's policy of not modifying /usr
but confining itself to /sw (with the sole
