Matt- Maybe it would make sense to have some post-install tests to verify that things work and, perhaps, to warn if the wrong perl is found in the path..
--Chris On Sat, Mar 3, 2012 at 1:37 PM, Matthew Kenworthy <[email protected]> wrote: > Hi Jim, > >> One thing I would say about about SciPDL is that it's practically too easy. > > This is a first - next time I'll package it in Pig Latin ;) > >> It would be nice if it opened up a readme file or webpage or something >> pointing saying what was installed where and pointing the user to next steps >> [or even troubleshooting] at the end of the installation (the only readme >> type documents are embedded in the installer, and the only way to access >> them is to run the installer again). > > Yes, that's a problem I've not addressed before. The next installer > should have "use /usr/bin/perl" in large red letters as the first > thing to read, as most people skip reading the README in the > installer. > > I'll also see about adding a final splash screen with the website and > a link to open a README as well. > > The 'which perl do I use' is a problem with the way other installation > programs quietly stop the Apple perl from being the default perl. I > would also delicately suggest that if you'd installed SciPDL right > from the start, you might not have had the collisions with the other > aborted PDL builds on your system. More big, red letters for the > installer, I think! > > If you want installation instructions for PGPLOT, drop me a line when > you're ready. > > Cheers, > > Matt > > -- > Matthew Kenworthy / Assistant Professor / Leiden Observatory > Niels Bohrweg 2 (#463) / P.O. Box 9513 / 2300 RA Leiden / NL _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
