>>>> "BAW" == Barry A Warsaw
<bwarsaw(a)cnri.reston.va.us> writes:
>>>> "nbecker" == <nbecker(a)fred.net>
writes:
nbecker> Some packages are mutually exclusive. The current
nbecker> packaging system doesn't handle that, and the UI doesn't
nbecker> tell you. For example, I found out that mailcrypt is
nbecker> incompatible with mailcryptng, in the sense that you must
nbecker> remove mailcrypt to install mailcryptng.
BAW> I hadn't noticed this, I think I installed both (not knowing what
BAW> mailcryptng was, but being able to guess from its name :-). Looks
BAW> like mailcrypting is working for me though.
The two packages are just different versions of the same lisp files.
If you install both, the result is basically random - just depends on
which files show up first in the load-path.
I think this is a general problem that may not have been addressed by
our current package design.
I think the first step toward a solution may be to at least provide a
mechanism to warn the user about conflicts.