* Stevan Little ([EMAIL PROTECTED]) [060305 16:53]:
> > to the two new perl books "Perl DBI-(Any)-cpan:TIMB"
> > and "Perl DBI-(Any)-mailto:[EMAIL PROTECTED]"
> Well, to start with, there is no
> C6PAN/SixPan/Whatever-it-will-be-called yet, so there is nothing to
> pre-register for.
On the German Perl Workshop last week, I stirred things up a little
with a BoF session about the subject. Amongst others, Andreas
and Juerd where present.
> Second, Perl 6 is still (at the very least) a year away from a
> (mostly) complete implementation,
> .... So pre-registration for namespaces in an unfinished language
> is a litte premature IMO.
So, in your opinion, it is easy to extend CPAN to contain perl6/parrot/
etc? Depends on the targets you set. Perl is especially known for its
extended library: it is the main reason we still exist. To make Perl6
a success, we have to take care of the library!
Just like new languages (like ruby) and ~features challenged Larry to
redesign our favorit language, should CPAN be evaluated against new
developments. Can we learn from SVN/SVK? Linux/GIT? Packaging like
rpm's, etc? The library world grew much more complex with languages,
character-sets, webdav, and super-fast networks at home. We do not only
need to host Perl6, but also perl5, pir, pasm, partcl, etc etc languages.
Quite a large number of people I spoke last week saw the need for major
changes in the general set-up of CPAN. But certainly the current one
is there to stay as well: CPAN is great. Maybe we can make it greater.
Say Perl6 is still 2 years away, than we need to hurry with new plans for
CPAN: when the currently eagerly waiting hurd of Perl programmers jump in,
it is too late...
> And lastly, I really don't like the idea anyway. It reminds me of the
> domain-name squatters of the mid-90s.
No, what I suggest is just like how cpan works now. But with a little
planning ahead.
> Some things may just need to stay the same, namespace intact. Anything
> else would IMO further the Perl 5/6 gap that will inevitably exist
> because of the depths of the language changes.
For me, it feels as a big mistake when our new archiving needs are seen
as a simple extra glue to the existing CPAN. If we need something smarter
over two years, we have to start designing it NOW, and building it tomorrow!
Before this becomes a real discussion about the future of CPAN: this thread
started with Yuval asking about having a Perl Wiki. It would be nice to
have a place where the community can be build, where the wide variety
of projects can be organized which are required for a good and large
new library. Were we can store presentations and teaching materials for
the new languages, and so on.
--
Regards,
MarkOv
------------------------------------------------------------------------
Mark Overmeer MSc MARKOV Solutions
[EMAIL PROTECTED] [EMAIL PROTECTED]
http://Mark.Overmeer.net http://solutions.overmeer.net
