On Wed, Apr 28, 2010 at 8:24 AM, Cosimo Streppone <cos...@streppone.it>wrote:

> On Wed, 28 Apr 2010 17:04:30 +0200, Michael DeHaan <mich...@puppetlabs.com>
> wrote:
>
>  On Tue, Apr 27, 2010 at 5:02 PM, Alan McKay <alan.mc...@gmail.com> wrote:
>>
>>> Hi folks,
>>>
>>> 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)
>>
>
> My experience is totally different. Debian is very active as a
> perl packager, but many module packages are just missing
> (obviously) or way too old to be useful.
>
>
>  CPAN's need to build things locally and update at
>> unpredictable intervals
>>
>
> I don't understand.
> You can control exactly when you want to update your index,
> if that's what you mean, or when you want to trigger updates.
>
>  (and frequently not building)
>>
>
> Again, my experience is that pretty much anything builds and tests
> correctly these days.
>
>
>  means I really wouldn't want to connect a production machine directly to
>> it.
>>
>
> I understand. But usually if you have a need for CPAN modules, and
> you are "serious" about it, you either:
>
> 1) manage your own CPAN mirror
>
> 2) use CPAN::Mini, that gives you full control of which packages
>   your local mirror should include, versions included
>
> 3) use local::lib, to make your CPAN environment self-contained
>   and not impacting on your OS-packaged perl and modules
>
>
>  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 ?


http://www.opensourcery.com/blog/hans-dieter-pearcey/packaging-cpan-modules-debian

or even cpan2dist ?


> There's active discussions in the Perl community to
> build OS-level packaging knowledge inside the current
> or future CPAN clients.
>
> Maybe that's the best way.
>
> --
> 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.

Reply via email to