Hi,
Zack Weinberg wrote:
> While updating my emacs configuration for 27.1 (now in unstable)
> I noticed that /etc/emacs/site-start.d/50git-core.el prints
>
> git removed but not purged, skipping setup
>
> and does not autoload either git.el or git-blame.el. This appears to
> be because /usr/lib/emacsen-common/packages/install/git does nothing
> when $FLAVOR is “emacs”:
>
> | # The emacs startup file looks for these files in
> | # /usr/share/${debian-emacs-flavor}/site-lisp/git.
> | # Installing to the generic /usr/share/emacs/site-list/git would be
> | # pointless.
> | [ "$FLAVOR" != emacs ] || exit 0
>
> This has been incorrect for quite some time - I’m not sure how long
> ago it was that (symbol-name debian-emacs-flavor) was changed to
> evaluate to “emacs” for the ordinary packages of GNU Emacs, but
> probably more than one release by now.
>
> I think a sufficient fix is to remove the above quoted lines from
> /usr/lib/emacsen-common/packages/install/git.
Thanks for reporting.
Strangely, debian-emacs-policy doesn't appear to be in the
emacsen-common package any more. Fortunately, it's in
https://www.debian.org/doc/packaging-manuals/debian-emacs-policy.
It looks like we can remove the '"$FLAVOR" != emacs' check because
Debian no longer provides multiple co-installable versions of emacs
(good!). I think if we remove the check this will simply do the
right thing.
Emacsen team: would a Breaks against emacsen-common (<< 3.0.0~)
be sufficient for ensuring we have a new enough version of emacs
for this to be safe?
Thanks,
Jonathan
