Ken Williams <[EMAIL PROTECTED]> wrote: > Hi David, > > Thanks for your feedback! > > On Monday, February 10, 2003, at 07:17 PM, David R. Morrison wrote: > > > > Hi Ken. I've been wanting to get some perl packages into Fink for some > > time, and this looks like a great start. The package worked well for > > me, > > although you do need to adjust where the man files are stored (Fink > > puts > > them in /sw/share/man, not /sw/man); > > Okay, I'll try to adjust that in the .info file. The perl installation > location variables are always so non-fun...
Well, if its hard to do with perl installation directly, you can do it in Fink's InstallScript (something like "mv %i/man %i/share/man" at the very end). [snip] > > One of the problems with the current situation is that there are those > > widely-followed instructions for replacing Apple's perl by a more > > recent > > version, but doing that breaks tools (like Fink) which may depend on a > > specific version. So it would be great to have a Fink way to install > > 5.6.1 > > and/or 5.8.0. > > Yeah, there could certainly be a fink package made for 5.8.0 and it > would work fine. Users could just adjust a /usr/bin/perl (and/or > /sw/bin/perl) symlink to get the different versions, or just use the > full paths. > > I think this means that the version number needs to be part of the > package name, though, and not just in the fink 'Version' field. > Probably perl5.6 and perl5.8, similar to the fink packages apache and > apache2, and the various versions of autoconf? > Yes, I agree. In fact, my understanding is that 5.6.0 and 5.6.1 would store files in different directories, right? So I think we actually need to call them perl5.6.1 and perl5.8.0 (in preparation for a later perl5.8.1, for example). I don't see any reason to build perl5.6.0 in Fink. [snip] > > Anyway, certainly if Fink itself is going to be used to compile some > > 5.6.1 > > or 5.8.0 modules, then /sw/lib/perl5/site_perl/ needs to be in @INC > > (although perhaps only in Fink? by setting it in Fink's > > /sw/bin/init.(c)sh > > perhaps?). > > Hmm - mainly because of my preferences for my own machine, I'd like to > keep the targetted location for regular (non-fink) CPAN installs > /Library/Perl/ even when using the fink perl-5.6.1. > /sw/lib/perl5/site_perl/ would be a good place for fink-installed > modules, or 5.8.0 modules, though. > I don't understand how this works, I guess. Can the user reset the targetted location, even if the one chosen at compile time was different? > > > > There are also interesting issues of whether, when Fink compiles a perl > > module, it should be doing so under multiple versions of perl. I'd > > appreciate hearing your thoughts about that as well. > > I was thinking maybe it should sense what perl versions are installed > (by probing for fink packages) and just install for any & all installed > perls, but I don't think that will actually work - what happens if the > user installs perl-5.6.1, then DBI, then perl-5.8.0? DBI for 5.8.0 > won't be installed. So that seems to point to using separate fink > packages for the perl versions. > Yes. Roughly what we need to do is to compile the module so that it will work with all versions of perl known to Fink, and store the results in the appropriately numbered sub-directories of /sw/lib/perl5. Now, I'm a bit over my head here, but my understanding is that lots of perl modules will be fine no matter which version they are compiled under, and copies of them could simply be deposited in the appropriate directories. But for other ones, multiple compiles might be needed? I don't know how one tells the difference between these, though. -- Dave
