Hi Jeffrey, On 20 May 2011 08:51, Jeffrey Thalhammer <j...@imaginative-software.com> wrote: > NOTE: This was also posted on perlmonks at > http://perlmonks.org/?node_id=905878. I'm trying to reach a wide audience, > so I'm posting it here too. > > Over the last few years, I've helped build private CPANs (DarkPANs or DPANs > as brian d foy calls them) for 3 different organizations. Each time I cobbled > together some combination of different CPAN::Site, CPAN::Mini::Inject and > CPAN modules with various shell scripts, commit hooks, and cron jobs. > Although they were generally effective, I feel they were clunky, highly > specialized, and hard to maintain.
You might want to check out: http://beta.metacpan.org/ the front and backend are here: https://github.com/cpan-api http://blogs.perl.org/mt/mt-search.fcgi?limit=20&search=metacpan has some history and discuss with them on irc.perl.org #metacpan - I've pointed them to your perlmonk post https://github.com/szabgab/CPAN-Digger also exists - I think Gabour is discussing if there is any overlap with #metacpan which they're discussing. http://blogs.perl.org/users/michael_j/2011/04/deploying-perl-code-with-git-locallib-minicpan-and-cpanminus.html is actually the setup we use at work, but this only works because we only have one version of all code for all projects. Hope that helps. Leo
