I just started using PPM from ActiveState at work and I really like it. I
would LOVE to get PPM for Ruby. Unfortunately Ruby does not seem to be on
ActiveStates radar. I know because I ask at least twice a month! : )
Nice article.
However these days I don’t think it is important to get a lot of mirrors
running.
It’s more important to have one master system with access interface and good
backup.
I was actually wondering earlier today if one sourceforge account could be
assigned to RAA and have all the RAA stuff, but I guess this violates some
SF policy.
Modules are already pretty well understood in Ruby, but there is the issue
with potential conflicts.
Perhaps there should be an official and an uoffical module scope e.g.
Alt::Test::Unit vs. Test::Unit such that major important names are not
introduced without consensus.
Very good content. I found the most striking observation in one of the replies:
“People started to install modules from CPAN because they were easy to install ;
they started to upload modules to CPAN because it was easy to produce an
installable tarball.”
When the discussion about bringing Ruby into CPAN began, was there any agreement
or suggestion that all CPAN mirrors would automatically mirror non-Perl code as
well? Or, conversely, if someone wanted to be a Ruby CPAN mirror, could the
Perl code be omitted?
I can see how having to buy into an all-or-nothing arrangement could be a
problem.
Perhaps there should be an official and an uoffical module scope e.g.
Alt::Test::Unit vs. Test::Unit such that major important names are not
introduced without consensus.
Mikkel
We could have one official repository. Other repositories can be created by
individuals and the end-user could use an interface to get those. For
instance in my PPM I have the following:
The first two are official Perl repositories. The second two I added
because they contain modules that I want. If you write the descriptor, in
say XML, then you could handle OS and installation stuff as well as package
tracking and version verification.