On Wed, Apr 28, 2010 at 8:52 AM, Cosimo Streppone <cos...@streppone.it>wrote:
> On Wed, 28 Apr 2010 17:36:03 +0200, Nigel Kersten <nig...@google.com> > wrote: > > On Tue, Apr 27, 2010 at 5:02 PM, Alan McKay <alan.mc...@gmail.com> >>> wrote: >>> >>>> >>>>> I was just digging through the archives and found some comments from >>>>> Sept 2008 about CPAN provider being immature. >>>>> >>>> >>>> Personally, I wouldn't want a CPAN provider -- if you can get content >>>> from OS packages (debian is particularly good about this) >>>> >>>> [...] >>>> >>>> Doing really minimal packaging for the CPAN modules you use, if not >>>> already packaged, would be worth it in my opinion. >>>> >>> >>> This way presents its problems too, many dependencies to repackage, >>> and I'd say too much work overall... depends on your needs, ofc. >>> >> >> Repackaging CPAN modules is reasonably trivial, and will give you a more >> consistent setup than writing a complex CPAN provider. >> >> Have you looked at dh-perl-make ? >> > > We're using dh-make-perl, and it doesn't handle dependencies > that are not already packaged, IIRC. sure. Is it really that much more work to insert appropriate dependencies compared to the alternatives though? It should also be relatively easy to change the way the dependencies are done such that even if it can't find the relevant packages it would know what they should be called though right? > > > >> http://www.opensourcery.com/blog/hans-dieter-pearcey/packaging-cpan-modules-debian >> > > I'll read it, thanks. > > Skimming through it, it seems the author is aware > of the limitations I was pointing out (having to maintain debian > control files, etc...) > If I cared about cpan these days I'd be looking at patching dh-make-perl to support generating the dependencies even if they don't exist yet. We do a similar thing here internally with packaging gems as debs. > > or even cpan2dist ? >> > > I think I looked at it long time ago. > Maybe time to see if it got updates. > > Thanks, > > > -- > Cosimo > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
