>One major reason to not use gems (or CPAN for Perl), is that it doesn't > play together with the OS packaging system. If an RPM (for example) has > installed a file, gems and CPAN will happily overwrite it, without recording > in the RPM database that the file is now owned by another package. If > you install an updated RPM, it will happily overwrite the gem/CPAN installed > file.
Yes this is true. To me it's about being consistent. If you are going the (rpm/deb packages) route keep using that for perl/CPAN. If not do all in CPAN or gem package management, not mixing two package managers. > For CPAN, there's the cpan2rpm program, which can create an RPM from a > CPAN package, which you can then install using the rpm or yum commands, > and I believe there's a cpan2deb program for Debian/Ubuntu. That gives > me the proper interaction with the normal package system. > I see there's a gem2rpm command available also. I haven't tried using > that, though. If there's a gem2deb command, I'd suggest the OP to try > using that. cpan2rpm works great for the most part and use that quite a bit. gem2rpm I personally had very mixed results (many things didn't compile) and oped to using gem directly (at least on centos/RH) On centos/RH there are very few pre-built gem rpms out there and was another decision maker. CPAN rpms on the other hand there are many available (DAG for example - http://dag.wieers.com/rpm/) -L --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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 -~----------~----~----~----~------~----~------~--~---
