Hello Monks

I have created a number of modules for a project using module-starter and Module::Install. Now it is time to release the project which requires the libraries, unfortunately, I am unable to release the modules to CPAN.

Instead of requiring the end user to check each library out of source control, make each library individually, then install the final application, can you please provide some suggestions for simplifying the install process.

My first thought is to write an install script, that performs the menial git clone, Perl Makefile.PL, make, etc. however, this will probably be the most time consuming method to maintain in the long run (not to mention I will have to write one for windows and one for Linux), so I would prefer to avoid this method.

My nest thought is to bundle the dependencies into a sort of "meta" package, and include the modules that need to be build; the problem with this is, I lose the benefits of fine grained revision control (not to mention what if Foo/Bar.pm is changed in the META package, but not in original source control...). I would prefer to keep each module under per module revision control because I will likely use these modules in other projects.

My final thought is to create a CPAN mirror. (And if I am going to go this route, are there any modules that integrate CPAN with ChiliProject/Redmine?) I don't really need to mirror anything on CPAN, (though it might decrease download time?), just host private code, (and only a handful of modules), so this seems like overkill, but theoretically, one could add the address of the private CPAN mirror and perform a `sudo cpan Private::Repo`, yes?

Any suggestions are welcome, thanks for taking the time to read.