On Mon, Jul 20, 2009 at 8:09 PM, Jan Hudec<[email protected]> wrote: [] > For the common case, I suggest saying that xmms2-core "Breaks: libxmmsclient4" > and libxmmsclient5 "Breaks: xmms2-core < 0.6" would describe where the > problem is. > > While it's not strictly true in all cases, I hope that a case where somebody > has both xmms2d and client on the same host, but never uses them together > (the only case the Breaks are incorrect) is insane enough that nobody > actually needs it.
The problem is that the libxmms2client[4,5] libraries have no direct dependency on xmms2-core and xmms2-core has no direct dependency on them. The reason for that is that xmms2 can be split between two computers, one running the daemon, the other one running a client. In that case the computer running the client only has the library installed, it could end up with both versions. In that case you could have for example gxmms2 linked against version 4 and an abraca against version 5. Only one of them would work while the other one could not connect. So I think the conflict should stay. It might make even more sense to add a conflict to xmms2-core against too old versions of libxmms2clientN and the other way round regards, Thomas Frauendorfer -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
