Re: Documentation: "How to get a CPAN module into debian"
2008/8/6 Jonas Smedegaard <dr@jones.dk>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sun, Aug 03, 2008 at 11:12:30PM +0300, Damyan Ivanov wrote:
>>-=| Jeremiah C. Foster, Sun, Aug 03, 2008 at 06:13:05PM +0200 |=-
>>> I am giving a talk for YAPC::EU about debian from a perl developer's
>>> perspective.
>
>>How about changing the title to "How to get the CPAN module I use in
>>Debian"?
>
> <nitpicking>
> The answer to that is "aptitude install lib<dashed-and-lc-name>-perl"
>
> So I suggest instead "How to get the CPAN module I use into Debian?"
>
> s/ in / into /
>
> </nitpicking>
>
Which is all very well if you don't mind using less than up-to-date
packages on Debian stable.
Compare the stable distribution version of CGI.pm got the Debian way
against the latest version available on CPAN and you'll find the
released CGI.pm is out of date by more than two years. Having said
that I'm happy to learn how to package the latest, or a suitable later
version, if someone is prepared to volunteer a bit of hand holding and
quality checking to get me going and there isn't anyone else that is
doing it already.
If I have a requirement for a more up to date version of a module, I
use the command 'cpan' to retrieve from CPAN but I have learnt to
watch the dependencies that occur.
My experience is that the new CGI stuff tends to be put in
/usr/local/share/perl/5.8.8 as opposed to /usr/share/perl5.
I believe there are even tricks which enable the install of a
completely different version of perl (5.10 or 6) documented 'out
there', but I haven't tried them yet.
If you really wanted to be completely sure any cpan module you install
is safely out of the way of any standard Debian install, I think you
need to look at install_dirs in the cpan configuration files but
search for that info to make sure. It's out there somewhere and I've
yet to implement it.
All this is not really novice stuff and if you don't need to do it
then use the lib<package>-perl stuff for system stability. Note you
then take on the responsibility of updating your packages installed
this way.
This http://www.debian-administration.org/articles/78 and this
http://www.debian-administration.org/articles/281 may equally be of
interest
Regards
L.
Reply to: