Re: Go (golang) packaging, part 2
Paul Wise <pabs <at> debian.org> writes:
> On Wed, Jan 30, 2013 at 11:15 AM, Chow Loong Jin wrote:
> > Having multiple package managers which don't know about each other on a
> > is evil™ (but in some cases, can be managed properly).
Meh, it’s evil, period.
> Some integration between dpkg and domain-specific package managers
> could be useful. With DEP-11, we could have 'cpan install Foo::Bar'
> tell you "Foo::Bar is available in your distribution's package
> manager, you can install it with apt-get install libfoo-bar-perl.".
That would be nice but not need integration, just replacement of
cpan with a small script ;-)
And, of course, having all of CPAN packaged properly. Which comes to…
> Also, GoboLinux apparently have a more advanced system for integration
> between their package manager and others like rubygems/cpan.
… something like that. Not quite. I don’t think it’s worth the pain;
it may be manageable for Perl, and maybe PEAR, and with even bigger
pain maybe even pypi, but not for Ruby and similarily hostile upstreams.
My co-developer (on the MirBSD side) benz has written a script that
almost automates creation of a port (source package) from/for a CPAN:
(It looks even MacPorts has adopted it!)
Of course, it needs some manual review (and someone’d have to convert
its output to Debian source packages, or merge it into the already
existing dh-make-perl which also somewhat worked when I tried it), but
it would make achieving this goal possible (and let running dpkg require
128 MiB of RAM or so, to fit the list of packages into it, I guess, but
even those Amigas have that).
//mirabilos (with his Synergy hat)
PS: Steve is not alone in thinking to kick it…