Sven Joachim <svenj...@gmx.de> writes:
> -Depends: ${misc:Depends}, emacs23, git-core, dpkg (>= 1.15.4) | install-info
> +Depends: ${misc:Depends}, emacs (>= 23) | emacs23 | emacs-snapshot, 
> git-core, dpkg (>= 1.15.4) | install-info

> +    emacs19|emacs2[012]|xemacs*)

> -(if (member debian-emacs-flavor '(emacs23))
> +(if (and (>= emacs-major-version 23)
> +      (not (featurep 'xemacs)))

I'm ok with the idea of both blacklisting old versions and only
supporting >= 23.

However, this week I went through all the
emacsen-{startup,remove,install} scripts that are in the archive. Almost
every single script does something in a unique (and buggy?) way. For
example:

emacsen-startup
===============

1) Some packages ship /etc/emacs/site-start.d/NNfoo and detect emacs
version using elisp. Some packages ship /etc/<flavor>/site-start.d/NNfoo
and do not need elisp check.

2) Some packages do the elisp check against debian-emacs-flavor, others
use plain "flavor" (that's a bug, right?).

3) Some packages handle removed but not purged packages in
/etc/emacs/sites-start.d/NNfoo and other don't. Some handle it by using
file-exists-p against an "*.el" file and some against an "*.elc" file.

4) Some packages call debian-pkg-add-load-path-item or setq load-path
(bug?) in /etc/emacs/site-start.d/NNfoo and others rely on subdirs.el to
do the work automatically. Is this perhaps a relic of some old emacs
version that did not have subdirs.el?

emacsen-install
===============

1) Some packages generate a byte-compilation log and save it in
/usr. Some put it to /tmp. Some remove it after installation, some
don't. Some even compress and log rotate byte-compilation logs...

2) Some packages create absolute symlinks to *.el files (against policy)
and only some use relative symlinks.

(The above list might contain errors since I didn't write proper notes
when I went through the packages, sorry about that in advance.

Do we really want to continue on this path?

With dh_pysupport there's debian/pyversions that lists the python
versions that a package supports. Would something like
debian/emacsversions make sense?

-Timo

P.S. If you wonder why I had

(if (member debian-emacs-flavor '(emacs23))

the reason was that I was subconsciously planning to replace it with

(if (member debian-emacs-flavor '(#EMACSVERSIONS#))

that dh would then fill out :-)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to