Conflict field for logical conflicts?
Hi,
should I set in package jed a conflict on a package jed-extra if
jed-extra enhances jed, but jed has changed its API and now jed-extra is
useless, i.e. it must be updated. jed-extra and jed can be installed at
the same time without harm, but jed-extra does not enhance jed anymore,
because it's not (directly) accessable from jed.
It's like a new API in firefox and the firefox-webdeveloper extension.
Should firefox declare a conflict on all extensions if the API changes or
is this a problem of the extension package?
Should an entry in the conflict field describe such a logical conflict or
only a conflict on the package/library level which prevents the packages
can't be installed?
Bye, Jörg.
--
Eine Blume geht über eine Wiese, sieht einen schönen Menschen und reißt
ihm den Kopf ab.
Reply to: