My first public, non-CPAN Perl release
I've been contemplating to do something like this for a while, but have only gotten around to it today. Here it is: SHARYANTO-Shortcuts-0.01.tar.gz. So far it's only hosted on github: http://github.com/sharyanto/releases-perl-steven (BTW, I also archive my CPAN releases there: http://github.com/sharyanto/releases-perl-cpan). The release is just a distribution that contains shortcut modules like DD (shortcut for Data::Dump), DDC (Data::Dump::Color), etc. The dist is not put on CPAN for obvious reason: the modules will terribly pollute the top-level namespaces.
With the current toolchain we have in Perl today, deploying non-CPAN modules should be easy enough.
My point for this post is that I think there exists a niche market for a platform that hosts non-CPAN releases but reuse the CPAN tools/architecture. Either private/commercial modules (the so-called DarkPAN), personal forks (e.g. I can have my own JSON::XS, there can be multiple modules with the same name from different author like on github), or things like what I published today (modules that do not comply with CPAN naming rules/convention).
A programmer (mostly Perl 5 nowadays).
My CPAN ID: SHARYANTO. I'm sedusedan on perlmonks. My twitter is stevenharyanto (but I don't tweet much). Follow me on github: sharyanto.
I have these popping up in my head as potential domain names: noncpan.com, noncpan.org, cpanx.com, cpanx.org, yourcpan.com, cpanforall.com.
It's a shame the Netherlands Antilles no longer exists. It could have allowed domain hacks along the lines of http://mycp.an/
We need to recreate the country first then. TIMTOWTDI.
That's exactly what Stratopan is for. Public repositories are always free, and a great way to distribute modules outside of the official CPAN mirrors.
I just tried creating an account at stratopan. Created a repository, one stack (and another). Could pull a CPAN dist, but could not add any dist tarball from my computer with error message: "Something went wrong: The default stack has not been set". Did I do something wrong?
No, you did everything right. You just found a regression (thanks for that).
Test case added, and new release shipped. Give it another shot.
For the moment I suggest sticking with a public repository. Private repositories aren't quite ready yet.