Weblog entry #138 for simonw
Running it can be "interesting", as CPAN doesn't have that concept of release, and so APIs may change underneath. The advice here is usually to manage Perl modules as Debian packages, but if you don't do that, you need to appreciate that things will break, and that you'll have to know some Perl (and extra stuff) to fix things.
Today I learnt;
Postgrey does different things depending on whether Sys::Syslog is installed.
Sys::Syslog changed its interface since Sarge was release.
Debian package maintainer for libembperl-perl (Angus Lees) knows more about Apache, and Perl than I think I want to.
They are right about putting the modules into Debian packages for revision control (I always believed them).
I suspect I owe Angus a beverage of his choice, but the upside is Angus doesn't know who I am. Both Exeter, and Edinburgh are a long way from Australia ;)
Comments on this Entry
[ Send Message | View dkg's Scratchpad | View Weblogs ]
dh-make-perl provides a simple way to debianize perl modules which aren't already in the repository. I find it useful.
Here's my telegraphic notes about doing this for one such package.
[ Parent | Reply to this comment ]
[ Send Message | View Steve's Scratchpad | View Weblogs ]
I do the same thing, with many of the perl modules require to run this code available upon my apt-repository.
There is a tendency for me to forget about updating them, but that might be better than blindly upgrading with no roll-back facility!
[ Parent | Reply to this comment ]