On Thu, Apr 14, 2011 at 09:51, Duncan Garland <[email protected]> wrote: > What’s the most common/best method of keeping the modules consistent between > systems? Since we joined the Catalyst/DBIx community we’ve become much more > dependent on that sort of thing.
You should be worried about distribution versions, not module versions. This is the sort of thing that rpm (and similar tools) was designed to solve. Nothing says you have to use the community RPMs. At $work, we build RPMs of the stuff we depend on. Then, we build RPMs of our stuff with dependencies on the RPMs we built of CPAN modules. Then, we have our own internal RPM repository that we deploy to prod from. That way, we control our upgrades, we know what we have where, and we don't worry about module $VERSION numbers. Rob _______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[email protected]
