On Tue, 18 May 2004, Michael A Nachbaur wrote: > Since the whole framework is 100% Perl, I feel it would be worth it to publish > it on CPAN, especially since the underlying Perl modules can be extended by > other users. This is the kind of problem I'd like to solve with a new top > level namespace.
The provisioning application sounds pretty cool, and it would probably get some feedback and use if it was published. Look over the custom modules you wrote and ask yourself the following for each one. 1. Does it stand alone on its own merits and provide a public function, or is it only really suitable when it's bundled with your application? 2. Will using an existing namespace in CPAN pollute that namespace with modules that don't work well without the entire framework of your application? Another thing to consider is does it need to be uploaded to CPAN in order to be public? Why not SourceForge, which is geared towards programming projects? Make one large tarball with the custom modules, include the other modules if necessary, or consider building a Bundle::(AppName) module to handle installing the rest. > -- > Michael A. Nachbaur <[EMAIL PROTECTED]> > http://nachbaur.com/pgpkey.asc > -------------------- Christopher Josephes [EMAIL PROTECTED]
