Ignoring Ned's inflammatory rant, he has a kernel of sense - > if you can abandon cpan, and use packages that are built in to your yum > repository.
As a Perl pro, i agree with this much with Ned's rant -- this is very good advice for C-based binary extensions (including library wrappers such as Tk), when the Perl it's to be used with is from OS Yum/Deb/... repo originally. You really really want all the C files built with the same toolchain and flags, and a single build system is easiest way there. [ If you build your own Perl from sources (not very hard really), building from CPAN works fine with it. If one is going to have lots of custom built modules, having a local perl is recommended, if only to avoid a sys upgrade updating /bin/perl and obsoleting all your local built modules ! For pure-Perl modules - without C/lib* dependencies - building from CPAN works fine. ] -- Bill Ricker [email protected] https://www.linkedin.com/in/n1vux _______________________________________________ Discuss mailing list [email protected] http://lists.blu.org/mailman/listinfo/discuss
