On 7/31/2010 3:47 PM, Jan Hoogenraad wrote: > > As primary an end-user of PDL, I'd like to comment on the texts below. > I do not need bleeding-edge support of PDL, just a version that works, > preferably an old and proven one.
OK > For me, it is important that is updated automatically on system > upgrades, and maybe on big upgrades of PDL. Also, updated dependencies > should be taken into account automatically, and uninstall should be > automated. Only the binaries distribution fit that. I think binary distributions are one of the two main ways to get PDL, the other being as a perl module from a source install. > In this respect, I'd like to have a package install given as FIRST > possibility, with source installs only if either the platform does not > support this, or if bleeding-edge support is needed. The binary install is already on the install page. What was left off was easy instructions for anyone who actually wants to install PDL (as a perl module). For them, and others with a development environment on their system, the simple source build instructions are the ones they need. In this case, PDL mostly does build out of the box. I may not build all possible dependencies but it does build a working PDL. > Chris Marshall wrote: >> On 7/31/2010 4:56 AM, Daniel Carrera wrote: >>> Hi Christian, >>> >>> On Sat, Jul 31, 2010 at 5:25 AM, Christian Soeller >>> <[email protected]> wrote: >>>> At the top of the 'Get PDL' page we need *simple* instructions >>>> >>>> 1) how to get the PDL source (CPAN, sourceforge) >>> The Manual Install page should cover this (it already covers CPAN). I >>> do *not* think that the Get PDL page should be polluted with this >>> information. Most people are not going to install PDL this way, and >>> those who do want to install PDL this way only have to click one link. >> >> There are two basic ways to get PDL: >> >> (1) a standard Perl module install >> (2) a binary package install >> >> and for now, and for PDL-2.4.7, the simplest >> way to get and build PDL will be #1: >> >> (1) download PDL source >> (2) extract the PDL-2.X.Y-tar.gz >> (3) cd to the directory created >> (4) perl Makefile.PL >> (5) make >> (6) make test >> (7) make install >> >> and if you have the cpan shell installed >> and available, the above reduces to this: >> >> (1) cpan PDL >> >> Binary packages for PDL are often quicker >> to get to but have the disadvantage of >> requiring knowledge of the per-platform >> package layout, program, and names of required >> packages in order to work successfully. >> >> In fact, the basic source install is the >> closest to being identical across all platforms >> and having that at the top level is appropriate >> to its broad scope and applicability. I stand by my preference that perl module users need to be able quick start with the standard source build (a.k.a. a cpan install if you have that installed). Maybe the third section could be install reference and the topic ordering could be: 'get binary PDL' 'get source PDL' 'PDL install reference guide' Cheers, Chris >> I think 3 sections on the "Get PDL" page: one for >> a "get source" install, one for a "get binary" install, >> and one for "manual install". I would like the >> unifying theme of this page to be "Get PDL". Right >> now, the best way to "Get PDL" is via the source >> build. _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
