Re: *more* relocatable perl

> Yeah that sounds like a bug. But I don't think anything uses either after install so I'm not surprised no one ran into that before.

I had a similar need (i.e. build various perls; then make /opt/perl or
whatever be a symlink to the directory containing the version I need
on that machine), and ended up having to patch Config.pm, as was
previously said in this thread, as well as similar changes.
What stumped me so far is some scripts (such as perldoc, IIRC?) don't
play nice, and don't let me "keep" a "#!/usr/bin/env perl" shebang:
they replace that with something like (going on memory, here)
"#!/usr/bin/env perl perl" as they add the "perl" bit, and I've not
yet found a workaround for _that_.

If I had a way to say hey, do whatever relocatable stuff you need with
the various "../../" to get at the "right" lib dirs, etc. _as well as_
keeping the shebang _as I gave it_ (i.e. "#!/usr/bin/env perl", as
it's up to the environment in my case to have the right directories in
the $PATH), I'd be firing on all cylinders.

Look forward to seeing some action on the relocatable bits, as I find
them very useful to keep abreast of new versions.
"plenv", "perlbrew" and the like are not an option for me.

-- 
Marco Fontani
perl -E'say v74.65.80.72'