Patrick Shanahan wrote: > * Dave Howorth <[EMAIL PROTECTED]> [06-20-07 17:11]: >> I would install any Perl modules from CPAN. > .... >> This link already tells you to use CPAN and gives direct links! But I'd >> use the cpan shell (man cpan for info) rather than install them manually >> or individually from the command line (follow 3.1.1.1.2 if you insist) > > the *usual* warnings should be applied here. > > openSUSE *is* and rpm-based system. Installation via cpan will > *not* be recognized by the rpm system and may cause conflicts and > breakage of installed items. Updates via yast, smart or ??? will > not recognize the cpan installed items and may cause conflicts and > breakage of installed items. > > YOU have been WARNED!
Have you ever encountered such a problem? This is another urban myth. I use Perl extensively, install all my modules from CPAN and have never seen this problem. The actual problems I do hear of mainly come from broken Perl packages shipped by some other distributions (not Suse :) Sure, on a production server, it's good practice to be very sure of versions, but in that environment the installation mechanism will follow whatever house policy is used for configuration management. Perl has an installation layout, which Suse and other distros follow, that is designed to prevent conflicts between modules installed from CPAN and modules installed via the distros' own mechanisms. YaST updates do not affect modules installed from CPAN and vice versa. Applications installed via YaST that use Perl modules can and should be configured in their packages such that they will not see Perl modules installed from CPAN if that would cause them a problem. Also, Perl programs run a large fraction of the web's infrastructure. The maintainers of important Perl modules take great care not to break backwards compatibility in the same way as for the C libraries etc. Cheers, Dave -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
