Good morning,
On 9/09/11 at 6:00 AM -0700, John Napiorkowski
<[email protected]> wrote:
If you install all your cpan dependencies into your perlbrew
managed perl you'd have to reinstall perlbrew from scratch if
you want to truly test your build system. For me, I like to
test my build by building everything from the start and I can
do that by either just deleting my local lib directory or
creating a new local lib. Also if you work on multiple
projects, or support several different cpan modules, I find it
prudent to have one local lib per project for everything to
be cleanly separated. I realize that leads to a lot of
possible duplication, but hard drive space is pretty cheap nowadays.
Thanks for all that. I can understand all those benefits but not
sure they apply in my case. I'm treating perlbrew as a
heavy-handed local::lib and since it's working for me I'll leave
it as-is.
Thanks again,
Charlie
--
Ꮚ Charlie Garrison ♊ <[email protected]>
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
〠 http://www.ietf.org/rfc/rfc1855.txt
_______________________________________________
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/
