Sloan wrote: > Dave Howorth wrote: >> Patrick Shanahan wrote: >> >>> I borked spamassassin some time back and had a devil of a time >>> replacing the cpan files with ones that openSUSE or SuSE could use and >>> update. It has been quite some time and I do not recall the >>> particulars, but would not touch that again with .... >>> >>> I cannot provide the particulars requested, but do not feel like a >>> reinstall to prove/disprove an action where I *was* burned :^) >>> >> I absolutely sympathise with your desire not to self-induce more grief! >> But without details, such problems will never get fixed. And we'll never >> know exactly what the cause was and exactly what package was to blame. >> >> In those circumstances, I feel that making sweeping accusations that the >> CPAN mechanism is the source of the trouble is entirely unjustified. > > We tend to learn quickly when burned. The problem seems to be mixing > components of perl from different worlds. I'm willing to do some testing > along these lines, on test machines, as time allows. > > Joe
Sloan wrote: > Maia is not available as a package, it's a manual install. The problem > seems to be mixing components of perl from different worlds. Indeed. My difficulty is that you made the claim that installing modules from CPAN broke Suse packages. As far as I can see, you have presented no evidence to back up that claim. The most likely explanation I can see is that a third-party package that you installed (maia) has dependency problems. Without details, it's impossible to establish whether maia itself is the source of the problem or one or more of the modules it uses is. In any event, all that I can see is that packages sometimes have bugs, not that the CPAN installation mechanism is broken or that it should not be used on Suse systems. Cheers, Dave -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
