Arlindo da Silva wrote:
1) The FAQ link on the nav bar of the home page http://perldl.perl.org is broken
It looks to be fixed now from http://pdl.perl.org
Strange, I still get an "Error 404" when going to http://pdl.perl.org/FAQ/
Now I get the same error. Maybe I was accessing the cached version.
That link was to
http://pdl.sourceforge.net/FAQ/ and the same can be access via 'pdldoc
faq' or '? faq'
from the perldl interactive shell.
2) Is there a way to search this mailing list past 2004?
I don't know of an easy way but you could download all the monthly
summaries, unzip them, then grep for strings...
This would work but it is somewhat high maintenance. I host my lists
on sf.net and there you get an automatic searcheable archive. Couldn't
you mirror your list at sf.net? Say, every message sent to
[email protected] would be posted at sf.net as well, so from 2008
on one would have a searchable archive. This mailing list archive is
PDL's "knowledge base", so it is important to have it easily
accessible.
Improved documentation and better access to resources are things I would
like
to see as well. There are issues with mailing lists and e-mail spam address
collectors but a wiki has just been started that could grow into a more
accessible
"knowledge base" for the PDL community.
- Is there an autoconfiscated version of PGPLOT somewhere?
The idea of a *complete* PDL build is a nice one, I don't know where one
would begin.
The SciKarl configuration, although only deployed on Macs as I
understand it, is a good start. I'd make sure a similar build can be
replicated on the target platforms (i586, x86_64, darwin ppc/intel,
cygwin, bsd's, etc), first building a static collection of
interdependent external libraries. This is much easier done if these
external libraries use the GNU autotools (if not, one can always add
it and contribute it upstream). Once the SciKarl collection is in
place, one can add the additional libraries and work your way up to
completeness. I'd be willing to help, but it may not be until Spring I
can find some time to dedicate to it. When is the next scheduled PDL
release?
I'm hoping for a patch release in winter 2007/2008 to fold it existing
patches
and portability fixes in preparation for some more extensive refactoring
starting
in the Spring 2008. We can always use help and ideas.
If you are interested, the latest CVS can be gotten from sourceforge.net
following the anonymous access instructions at
http://sourceforge.net/cvs/?group_id=612
with PDL as the modulename. We're working to migrate from CVS
to SVN as the version control system which should simplify things.
Much of the PDL functionality takes advantage of 3rd party libraries with
their own release schedules and licensing issues.
That is right. One approach is to update the external libraries on a
slower time scale, on a "need to update" basis, at least for the
stable libraries. Sometimes tracking the trunk only leads to
instability with nothing much to gain.
Work is underway to improve the robustness and availability of PDL.
This is good to hear.
I'm not sure what you mean by an
"autoconfiscated" version of PGPLOT.
I just mean based on GNU autotools: configure, make, make check, make
install. Last I tried, building PGPLOT was not exactly automatic.
Thank you for your quick response.
Arlindo
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
