Previously Fabien Ninoles wrote: > However, a recent thread in debian-perl (hey, it was only two weeks ago!) > talks about this issue and we get two differents solutions: a CPAN::Debian > that let dpkg know about the cpan modules, their files locations and what > they provides; and a deb-make target for perl modules that let a maintainer > create a standard skeleton for all modules, with a special cpan-update target > in the debian/rules file. Hmm. Can someone please summarize the problem, the proposed solutions and what might need to be changed in dpkg? Please take into accont that I don't program in perl at all and have never used CPAN. Wichert. -- _________________________________________________________________ / Generally uninteresting signature - ignore at your convenience \ | wichert@wiggy.net http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Attachment:
pgpY2zoGUMadY.pgp
Description: PGP signature