Chris: Sounds like a fine idea to me! --Doug Hunt
[email protected] Software Engineer UCAR - COSMIC, Tel. (303) 497-2611 On Sat, 1 Aug 2009, Chris Marshall wrote: > PDL users and developers- discussion welcome. --Chris > > ACTION: > > Add explicit dependencies to the git PDL Makefile.PL > for modules that are needed for essential PDL services. > > That would make PDL builds more transparent, would > allow us to evaluate the impact on usage, and would > set us up better for the proposed factorization of > PDL into a core module component with external modules > providing key functionalities. > > Then a PDL bundle(s) could be used to distribute the > modules. > > DISCUSSION: > > I tracked down a t/dumper.t test failure that > apparently resulted from a bug in the underlying > Data::Dumper module that has been fixed in more > recent versions of Data::Dumper. > > Rather than hack around the bug, I reported the > problem to the Data::Dumper folks, and then added > Data::Dumper 2.122 as a prerequisite for PDL. > (This version appears to have the problem fixed) > > The thought was that saving piddle data to files > was an essential capability of PDL and should be > fully supported rather than quietly skipped if > it did not build successfully. That is what we > do in many of the optional external dependencies > such as GSL, Minuit, PROJ4, OpenGL,... > > After that addition, I was tracking down another > failure, in t/storable.t, and determined that we > actually use the basic Storable module and then > augment it to implement PDL::IO::Storable. We > appear to be requiring Storable but PDL::IO::Storable > will not work without it. > > A grep through my blib/ got these modules being used: > > Carp > Config > Convert::UU > Cwd qw(cwd abs_path); > Data::Dumper > DynaLoader > English > Exporter > ExtUtils::MakeMaker > File::Basename > File::Spec > FileHandle > Filter::Util::Call > Getopt::Long > IO::File > PGPLOT > POSIX qw( log10 ); > Pod::PlainText > Pod::Text > SelfLoader > Storable > Symbol qw/ gensym /; > Text::Balanced > Tk > > in some .pm file. Some of these are provided by the > core perl modules, others may be used conditionally. > The proposal is to put everything that is actually > used (required?) into the prerequisites list and see > how things work from there. Things that are not > necessarily required should be listed as a perldl.conf > option so we are all clear. > > > _______________________________________________ > Perldl mailing list > [email protected] > http://mailman.jach.hawaii.edu/mailman/listinfo/perldl > _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
