Small side note: how about changing the code to automatically insert such a dependency if the type is "Perl: x.y" ? This way it can't be forgotten. Would there be any cases where this automatic behavior is not desirable?By the way, the versioned perl module packages are supposed to state a build-time dependency on "perl5.x.y-core", which guarantees that the appropriate binary is present to compile the package.
In addition to moving the $perlcmd code to get_perl_dir_arch(), I corrected
some implementation errors which had crept in as 2 or 3 different people
had modified that code in the past few months.
There is one residual problem with all of this. For backward
compatibility, we are still storing files for non-versioned perl modules
packages in /sw/lib/perl5 and /sw/lib/perl5/darwin. However, the
files in /sw/lib/perl5/darwin won't be found by perl 5.8.1. To get
around this, I'm thinking of having fink install a symlink
/sw/lib/perl5/darwin-thread-multi-2level -> /sw/lib/perl5/darwin.
Does this sound like a good idea?
Well, I don't see any other solution ATM, so at least from my POV it seems to be the best we can do...
Max
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
