> > > I'm not familiar with the difficulties there. If there is > a standard non-system location to put perl modules, I would > imagine that the SciPDL build could be configured to use > that (e.g., I never install PDL in the system paths but use > a personal repository). You could set up something for SciPDL > to use and then add the needed paths. It does seem that PAR > distributions could simplify a lot of this sort of thing but > I'm not suggesting such a big change for 2.4.10. > > SciPDL are a set of statically built Perl modules and PDL into some specified perl location, currently /usr/bin/perl. I don't have the perl-fu do do anything more than that :)
> I was thinking of using PAR for the Devel::REPL and its dependencies. > My experience is that if you do a cpan install Devel::REPL it usually > gets messed up somewhere. What I've done is to get a list of all > the dependencies and then install them in the order required rather > than tossing the mess to cpan and hope it all gets sorted out (usually > not in my experience). > > Yes, that's exactly what I hit! Then a PAR of *that* would be made so you could use pdl2 just by > adding the 'use PAR' magic lines at the right places. The idea is > to have a 1-click version of "install all the mess for Devel::REPL > to work". > > Hmm, interesting! I'd be interested to see that in action.... Cheers, Matt
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
