Re: Best practice for version control of locally installed CPAN modules

2006-02-28 Thread Steffen Mueller
Matisse Enzer wrote: #2 has it's benefits too - you could even mirror all of CPAN, and just maintain a script with "install" commands to install the versions you want; install "KWILLIAMS/Module-Build-0.27_04.tar.gz"; etc. That makes both upgrading easy and makes your build proces

Re: Best practice for version control of locally installed CPAN modules

2006-02-28 Thread Michael Peters
Matisse Enzer wrote: > > On Feb 27, 2006, at 6:59 PM, Tyler MacDonald wrote: > >> #3 seems like the lowest maintenence. Maintaining on a .tar.gz in CVS >> seems easier than integrating diffs of the newest version whenever >> you want >> to upgrade. >> > > We definitely do NOT want to be i

Re: Best practice for version control of locally installed CPAN modules

2006-02-28 Thread Matisse Enzer
On Mon, February 27, 2006 8:14 pm, Dr Bean wrote: > There is some interesting advice in the subversion book. > >Linkname: Vendor branches > URL: > > http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html#svn.advanced.vendorbr.general I've read this section and i

Re: Best practice for version control of locally installed CPAN modules

2006-02-28 Thread Matisse Enzer
On Tue, February 28, 2006 12:35 am, Steffen Mueller wrote: > The upside is that it might be using less bandwidth in the long run. For us bandwidth is not at all an issue. > You might want to look at > http://search.cpan.org/~rjbs/CPAN-Mini-0.40/lib/CPAN/Mini.pm and > possibly > http://search.cpa