*** Christopher Mahmood (ckm@suse.com) wrote in suse-security on Mar 4, 2002:
[...] I don't see how the update could have overwritten your version of PEAR unless you installed it in /usr/bin and /usr/share instead of /usr/local/bin and /usr/local/share. If you did that then you shouldn't be surprised that rpm overwrote it.
And isn't there also the option to build rpm archives from what you install by your own and be warned if an other package is going to overwrite a file of another - your - package? In the meantime I build rpms from what I've installed from tar balls and developed by myself since it's easy as nothing. Best regards Henning Hucke -- It wasn't that she had a rose in her teeth, exactly. It was more like the rose and the teeth were in the same glass.