We are slowly replacing a large legacy monolithic application with a (somewhat monolithic) Catalyst app. There's about a dozen or so developers working mostly on three development boxes. Much of the code is placed into standard (CPAN-style) modules. Everything is under revision control (subversion).
If you are in a similar work environment how to you manage your internal modules? Do your developers use something like local::lib or perlbrew to manage their own environments? Do you run a local CPAN mirror and inject your own in-house modules (so that app dependencies can be installed automatically)? If so, how and when do modules under revision control end up packaged and how do developers manage module dependencies? -- Bill Moseley [email protected]
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
