Package: gaphor Version: 0.8.1-5 Followup-For: Bug #365465 as upstream gaphor supplies a small subset of zope3 and zope-interface files, installing gaphor as-is would naturally conflict with those other packages. this conflict could be resolved in several ways, with different levels of accuracy: 1. in the case, that the zope/* files gaphor depends on have been somehow customized, those files should install in a gaphor_zope subdirectory of site-packages. other gaphor files should be consequentially updated, and no conflict should occur with generic zope*. this might btw be the real case, since the files in zope/* differ from zope-interface, at least. 2. otherwise, the most straight forward alternative would be that gabor depend on those zope* packages. since zope is a huge package with heavy installation implications, this would be suboptimal too. but on the other hand, the zope-interface package is a rather small one, and many non zope related packages depend on it. i'd therefore suggest you may comment-out the zope.interfaces related lines from setup.py, and depend on zope-interface. having the zope maintainer export a larger zope functionality to other packages would let you end up in depending on the other zope-dependency package, as well as zope3 itself. 3. my principal reason not to aggree with your solution (to conflict with both zope3 and zope-interface) is that i use several non zope related packages that depend on the zope-interface ;-) .
best regards, alex -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-486 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
