Re: What to tell Module::Build, and where?

Avoid the whole mess and keep two perl installs. Have the system perl (/usr/bin/perl or /usr/local/bin/perl) which aptitude maintains. Then, have your own personal perl (~/bin/perl) which has your own modules. Check out Perl::Install for an easy way to install it. Patches welcome.

My criteria for good software:

Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Comment on Re: What to tell Module::Build, and where?

Replies are listed 'Best First'.
Re^2: What to tell Module::Build, and where? by rudder (Scribe) on Apr 21, 2008 at 06:29 UTC
I agree, though usually keep my own perl in either `~/opt`, or else maybe `/opt`. This way, you can keep all of it under the same tree (which makes an uninstall very easy (i.e. `rm -fr ~/opt/perl-5.10.0`), if that's ever necessary). I've never used Perl::Install. I just read the build instructions that come with Perl and go to it.	[reply]
Re^3: What to tell Module::Build, and where? by dragonchild (Archbishop) on Apr 21, 2008 at 09:26 UTC
I would normally agree, but I found myself having to install Perl over and over as part of a deployment process. So, I threw this together as a first-pass CPAN-ization of my scripts. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]
Re^2: What to tell Module::Build, and where? by stiller (Friar) on Apr 21, 2008 at 06:37 UTC
Nice idea! I made an extra account with low privileges and tried, but the installation of Perl::Install wants to write to `/usr/local/bin` and so stopped there. I'll try again with some broader permissions, but I think it should do that operation on something like `~/local/bin`?	[reply] [d/l] [select]
Re^3: What to tell Module::Build, and where? by dragonchild (Archbishop) on Apr 21, 2008 at 09:24 UTC
As I said, patches are most welcome. This is the first CPAN distro I made that has installable scripts in it, so I probably screwed up somewhere. The scripts run on their own, so you could just download them from cpan.org and go from there. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]