Sloan wrote: > Dave Howorth wrote: >> joe wrote: >> >>> That's an easy one - perl tarballs are ignorant of your package database, >>> and >>> a cpan install will simply overwrite your existing suse package without >>> hesitation or awareness of the fact. Likewise, rpm is unaware of the cpan >>> installed packages lurking there and will overwrite them in case of >>> conflict. >>> >> This shouldn't happen. There is a built-in mechanism to prevent such >> conflicts. Can you please supply specific details of any packages where >> this has occurred? What is the package name, Suse and CPAN versions, >> which files have been overwritten (ls -l would be useful). And which >> applications were broken as a result? > > It's been some months - I don't remember all the packages and versions > installed anymore, but I do remember clearly that upon installing some > cpan packages my maia mailguard system promptly broke. I was able to get > it back up and running only after surgically removing every trace of > perl and reinstalling it from rpm packages.
Without specific details it's practically impossible to say what happened or to fix any such problems. It would be much better to file a bug report at the time, when details are fresh. I can't find maia when I search the Suse repositories. Which package is it in? Cheers, Dave -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
