On Tue, Apr 1, 2014 at 8:44 PM, Les Mikesell <lesmikesell@xxxxxxxxx> wrote:
> On Tue, Apr 1, 2014 at 1:50 AM, C. L. Martinez <carlopmart@xxxxxxxxx> wrote:
>>
>> http://lists.centos.org/pipermail/centos/2014-April/141871.html
>>
>> about the problems you can find building perl modules for CentOS
>> releases (new or old).
>>
>> I agree with John R. Pierce: cpan is very very bad tool ( in fact, I
>> hate it) to build perl modules for CentOS systems, breaks all other
>> perl modules. I need to use several perl modules in several servers in
>> my dept. and after some tests, I migrate to FreeBSD due to easy
>> install perl modules with poudriere suite.
>>
>> But, anyone knows if it is possible to build a confident devel
>> environment under CentOS with some tool to build rpm's perl modules
>> without breaking anything in CentOS systems??
>>
>> Maybe, it is a good idea to create a CentOS Perl SIG :))
>
> Pretty much everyone needs EPEL for something - so it is not enough to
> not break anything in CentOS base, but you also need to not
> break/conflict with/replace anything in EPEL. So really, the best
> approach would just be to add any missing modules to EPEL.
>
Thanks Les, but EPEL here it is not an option. I need a lot of perl
modules that it doesn't exists in EPEL repos. Yes, I can use some (a
few) of perl modules published in EPEL, but they are outdated ... And
it is another problem ..
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
