But why shouldn't perl584-core specify /sw/bin/perl5.8.4 as the
startperl option? Specifying /sw/bin/perl seems inherently broken since
that file is not included in the -core package.
-Ben
On Nov 9, 2004, at 5:52 AM, David R. Morrison wrote:
On Nov 9, 2004, at 3:18 AM, Ben Hines wrote:
perl5.8.4-core does not install /sw/bin/perl, but its Config.pm has:
startperl='#!/sw/bin/perl'. This messes up my help2man package. I
tell it PERL is /sw/bin/perl5.8.4 but then it asks for
$Config{startperl} and perl says /sw/bin/perl. So it no work. I want
it to use fink perl if its there.
Shouldn't fink perl584 be configured with /sw/bin/perl5.8.4 as the
startpath?
(from perl's configure)
What shall I put after the #! to start up perl ("none" to not use #!)?
[/sw/bin/perl]
-Ben
Packaging perl for fink has been a tricky problem. Basically, perl is
not designed with the idea that a system would have more than one perl
installation on it at a time.
I've tried to compile perl with the same compile-time options as Apple
uses (other than the prefix), to increase the chances of
compatibility. But then, to avoid having various fink-installed perls
stomp on each other, /sw/bin/perl itself is separated out to a package
of its own (perl584, in the case being discussed).
I'm assuming that if you have complied something with perl 5.8.4, you
don't want it to be accidentally run with perl 5.8.0, right? So
perhaps your package should Depend on perl584, not just perl584-core.
-- Dave
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
