[Chicago-talk] Testing a module installation
warren.lindsey at gmail.com
Sun Jan 25 10:16:20 PST 2009
Well, you probably already have additional modules in your existing
Perl library, so you will need to install a fresh perl anyway. Once
that is done you could either:
1. Tar up directory, perform module install, test, erase, untar
2. LVM supports snapshots. Instead of restoring the entire VM, just
rollback to the previous snapshot.
On Sat, Jan 24, 2009 at 6:57 PM, Jay Strauss <me at heyjay.com> wrote:
>> Two answers: one slightly unixy, one very unixy.
>> 1) Build a new perl with -Dprefix= and install it, then make sure to
>> use /path/to/that/perl -MCPAN -e shell to install your module. That perl's
>> compiled-in @INC will have paths under the prefix, so it won't see anything
>> that you might have installed through your "system perl". However if you're
>> doing any XS, it may well pull libraries from your system library path, so
>> the test is a bit less than perfect.
>> 2) Short of a fresh install in a VM, there's a fresh install in a chroot. I
>> know that Debian, Redhat, and FreeBSD all have tools to make this quite
>> simple, and I'm sure that other systems do as well. Debian's build procedures
>> for their package repository actually work this way :)
> I'm running on Ubuntu. I'll have to investigate how to do #2.
> Seems like there should be some easy way.
> Chicago-talk mailing list
> Chicago-talk at pm.org
More information about the Chicago-talk