将CPAN模块转换成Debian软件包的最佳方法是什么？ [英] What's the best way to turn CPAN modules into Debian packages?

问题描述

每当我使用具有特定处理程序包管理方式的任何风格的系统时，我都会坚持使用该标准来管理我的Perl模块。 在罗马等等

Whenever I work on a system of any flavor that has a particular way of handling package management, I try to stick with that standard for managing my Perl modules. "When in Rome, etc."

例如，在使用ActivePerl的Win32系统上，我使用PPM进行一切，并使用了很好的 PPM :: Make 。在RedHat系统上，我更喜欢使用RPM。

For example, on a Win32 system using ActivePerl, I use PPM for everything and use the great PPM::Make. On a RedHat system I prefer to use RPMs.

现在我正在使用Debian系统，发现自己需要一种方式来转换任意的CPAN或CPAN风格分配到一个deb。

Now I am working on a Debian system, and find myself in need of a way to turn an arbitrary CPAN or CPAN style distribution into a deb.

Google显示的选项如dh-make-perl，CPANPLUS :: Dist :: Deb和CPAN :: Packager :: Builder :: Deb。

Google shows options like dh-make-perl, CPANPLUS::Dist::Deb and CPAN::Packager::Builder::Deb.

有谁拥有这些不同工具的经验，有什么建议可以使用或避免吗？

Does anyone with experience with these different tools have any recommendations as to what to use or avoid?

最好的办法是处理建筑物从标准CPAN模块的deb文件？

What's the best way to handle building deb files from standard CPAN modules?

我发现

I found an article by Hans Dieter Piercy on this subject - he suggests, for his own needs, CPANPLUS tools. Under some circumstances he recommends dh-make-perl. Jeremiah Foster (who wrote the article brian d foy points to) responds to HDP and makes a case for dh-make-perl.

还有一个 idimmu.net上的一篇文章描述使用dh-make-perl。

There's also a post on idimmu.net that describes using dh-make-perl.

ATM，我倾向于dh-make-perl，因为这是三次推荐（brian d foy as代理Jeremy Foster，idimmu.net作者和hillu）vs一次为CPANPLUS

ATM, I'm leaning toward dh-make-perl, since that has been thrice recommended (brian d foy as proxy for Jeremy Foster, the idimmu.net author and hillu) vs once for CPANPLUS

推荐答案

dh-make-perl 很好地照顾了来源的重复提升和猜测信息。对于我已经打包成Debian软件包的几乎所有CPAN模块（官方或仅供内部使用），它已经正常工作。

dh-make-perl does a good job in taking care of the repetitive and heavy lifting and guessing information from the sources. It has worked correctly for almost all of the CPAN modules that I have packaged up as Debian packages (official or for in-house use only).

那就是说，软件包只能被认为是Debian软件包的起点。 dh-make-perl 将警告提示放入自动生成的内容中，例如 debian / control （即包的描述和依赖关系）和 debian / copyright （许可信息）。

That said, the resulting package should only be considered as a starting point for a proper Debian packages. dh-make-perl puts warning notes into the automatically generated such as debian/control (i.e. description of the package and dependencies) and debian/copyright (licensing information).

为了回应Manni，我相信它是伟大的想法使用操作系统或发行版提供的软件包管理工具，而不是针对它们。在Debian的情况下，这意味着将东西放入 .deb 包中并安装它们。 Perl的构建工具和CPAN在提供跨平台构建环境和分发源代码方面做得非常出色，但与现代Linux发行版中的软件包管理工具相比，它们执行次优，因为通常需要额外的手动干预

In response to Manni, I believe that it is a great idea to work with the tools that the OS or distribution provides for package management, not against them. In the case of Debian, this means putting stuff into .deb packages and installing those. Perl's build tools and CPAN do a great job of providing a cross-platform build environment and for distribution of the source code, but compared to package management tools in modern Linux distributions, they perform suboptimally, simply because extra manual intervention is often required that is less easily automated across multiple machines than rolling up a package.

（对于一次性和测试安装，安装到 / usr / local / / code>并使用 stow（8） 作为一个穷人的包裹经理可能没关系。）

(For one-off and test installations, installing into /usr/local/ and using stow(8) as a poor man's package manager may be okay.)

即使您只是构建您自己使用的包，请考虑联系Debian Perl Group如果您认为有问题的模块可供其他人使用，并且有人赞助上传到Debian。

Even if you are just building the packages for your own use, consider contacting the Debian Perl Group and have someone sponsor an upload to Debian if you feel that the module in question is of use for other people.

这篇关于将CPAN模块转换成Debian软件包的最佳方法是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！