Speaking also as a Debian packager, and notwithstanding Dominique's comments that we dislike Module::Install, I'd like to provide some additional clarification:
On Mon, Mar 22, 2010 at 4:11 PM, Dominique Dumont <domi.dum...@free.fr> wrote: > Module::Install raises a lot of problems downstream. I often hear Debian > packagers complaining about it. This is true, however, it's more about the fact that there are multiple different versions of Module::Install floating around in our packages (since they are embedded with each distribution, by its nature). Subsequently, sometimes we've discovered bugs that we need to add overrides for during building, cf. http://pkg-perl.alioth.debian.org/debhelper.html I think one other "issue" is that people are upset with the idea of having to add copyright information for files in inc/Module/{Install/*,Install.pm}, but this is largely mitigated with the copy-and-paste stuff here, cf. http://pkg-perl.alioth.debian.org/copyright.html However, the Module::Install maintainers have been on friendly terms with the pkg-perl group and I know of no outstanding issues we have with its usage. If there are, then it's incumbent upon us to report bugs against Module::Install accordingly, and coordinate with them to find a solution that makes everyone happy. > Module::Build works fine and does not raise such problems. Module::Build's new bundling feature provides the same advantages and many of the same disadvantages involved with Module::Install. However, I have not seen its usage really out "in the wild" as of yet. Cheers, Jonathan
