G T Smith wrote:
CPAN perl repository stuff do not normally affect the non-perl libraries on the host system (it will complain if the version of a non-perl library is not correct but it will not replace it, it will update any perl related dependencies). e.g. The cdio perl library refuses to install because it cannot compile against the SuSE libraries. It is up the user to install the appropriate libraries or non-perl executable components a module requires within the context of the OS...
I am using a number of CPAN components which do not exist in the SuSE repository in rpm form. Perl is its own universe and once you have installed perl components from CPAN it is probably unwise to update with SuSE perl rpms and it is probably a good idea to continue maintaining perl with CPAN only....CPAN has its own mechanism for tracking perl components and updates on the system, and once one is committed to CPAN I would say the reverse is more accurate, SuSE rpms may damage the perl configuration...
That's not supposed to happen either. Look at your @INC: perl -e '{ print "@INC\n" }' You should see site_perl directories that are used by modules installed from CPAN and vendor_perl directories that are used by modules installed from Suse rpms. Applications from Suse rpms should have their @INC set so that they never see the site_perl directories, which is why I'm asking Joe and Patrick for details of the offending programs they say they've seen. Conversely, applications that you build yourself will use any modules installed from Suse rpms by default but will give preference to any that you install from CPAN. Any Suse rpms subsequently installed won't affect modules installed from CPAN. Again, if you know of any that actually do, please say what they are! Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org