On Saturday 18 September 2010 15:48:07 you wrote: > > process through negotiation: > > "this app needs X=<ver>,Y,Z"... "OK, can meet"..."here's the app" > > But app Q=<ver>,T,F > > But app T installs a file /usr/share/icons/kewl.png > And app Y also installs a file /usr/share/icons/kewl.png > > Since T and Y conflict (rpm won't let you install both unless you're a > ninja), so does Q and X. Very uncool, especially since they are all > "compliant" according to your definition.
Then both T and Y and non-compliant as they install stuff outside their own directories and X and Q would still be conflicting (and non-compliant) if they bundled T and Y instead of depending on them externally. We're running in circles. If your dependency conflicts with something, so would your package if it bundled it, external dependecies do not change this in any way (if anything, they can ease constraints as by depending on virtual packages). Best regards, Attila Csipa _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
