Bug#533725: slime: please refrain from declaring conflicts

Aaron M. Ucko ucko at debian.org
Sat Jun 20 01:15:04 UTC 2009


Package: slime
Version: 1:20090616-1
Severity: normal

slime has recently taken to declaring

Conflicts: emacs21, xemacs

because it (per upstream, AIUI) only supports GNU Emacs 22+.  As far
as I'm concerned, you're welcome to limit support to whatever subset
of emacsen you wish; however, the approach you've taken is a bit
draconian, at least in intent.  (In practice, the conflict with
"xemacs" is ineffective because there hasn't been so much as a virtual
package by that precise name in years.  FWIW, "xemacs21" is another
matter.)

Instead, could you please modify your emacsen-common "install" and
"remove" scripts to run only for the flavors you're willing to
support?  Instead of the current logic, they could both start off with

case "$FLAVOR" in
    emacs2[2-9] | emacs-snapshot ) ;; # supported; proceed!
    * ) exit 0 ;;
esac

after setting FLAVOR and PACKAGE.

In conjunction, please arrange for the startup code to load
slime-autoloads only if package-dir actually exists; that's actually
good practice regardless to avoid errors when slime has been removed
but not fully purged.

Thanks!

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash





More information about the pkg-common-lisp-devel mailing list