# from David Golden
# on Tuesday 13 April 2010 10:48:
>Our proposal is for Perl 6 modules to be uploaded into a 'perl6'
>subdirectory of a CPAN author's directory like so:
>
> ...D/DA/DAGOLDEN/perl6/Foo-Bar-1.23.tar.gz
This would require changes to any tools which think that
D/DA/DAGOLDEN/*/ are all simple subdirectories with no special
conventions attached to them.
I would prefer that the perl6/ part of the tree be created a few levels
up - e.g. perl6/authors/id/D/DA/DAGOLDEN/.
Aside from being able to start uploading without changing PAUSE, what is
gained by putting the perl6/ directory in this deep, and how many other
things are going to have to permanently bear the complexity of having
this one special directory land in the middle of the existing
filesystem? Further: where (if they exist at all) will the various
symlinks go for perl6 dists?
I'm thinking that rooting a completely new tree at /perl6/ might also
make it possible to repurpose perl5 dist tools for handling perl6 code
by simply appending '/perl6' to the base mirror uri. (Assuming that we
make the perl6 tree look substantially similar to the existing one.)
>PAUSE already supports uploading to subdirectories today, so the
>functionality exists NOW without any changes to PAUSE. It requires a
>*convention* of authors uploading their Perl 6 distributions to the
>right place ...
>...add
>radio-boxes to the PAUSE upload page to indicate Perl 5 or Perl 6 and
>to place Perl 6 distributions into the proper directory without it
>having to be specified explicitly.
If you're changing the upload tool and indexer, it would seem that
making them auto-detect perl6-ness (via the metafile?) would be less
error-prone for users.
I wonder: is it possible/feasible to run a second instance of PAUSE as
a perl6-mode without extensive changes? Presumably, requiring a
metafile should put the indexer into a flow where it isn't trying to do
anything perl5-specific, so then you just need some new tables?
Or, a perl6-only fork/rewrite of it if someone is so inclined.
--Eric
--
software: a hypothetical exercise which happens to compile.
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
