Yes, this is a known "feature" of RPM. A package installs into the
location for which is was rolled. That this causes sometimes
trouble (especially if multiple OpenPKG instances exists
or a vendor RPM) is known and certainly nasty. Unfortunately
we still have no solution for this. The only possibility
is to patch RPM for OpenPKG to reject those installations.
This will be kept on our TODO list for later consideration.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Bug Database Interface www.openpkg.org/bugdb
Bug Database List [EMAIL PROTECTED]
