site-start.d init file handling for Emacs flavours (was: Re: RFS: gnus (second try))

[Tommi Vainikainen <thv+debian@iki.fi>]

Peter S Galbraith <psg@debian.org> writes:
> Tommi Vainikainen <thv+debian@iki.fi> wrote:
>> However in addition to that, there is now Piuparts error[1], which I
>> understand is related to my earlier mail[2] on debian-emacsen, which did
>> not trigger any responses. Can anyone here clarify what is correct
>> approach for handling removing of site-start.d init-files for Emacs
>> addons, please?
>> 
>> [1] http://piuparts.debian.org/sid/source/g/gnus.html
>> [2] http://lists.debian.org/debian-emacsen/2009/07/msg00000.html
>
> I don't think I do anything special about those files.  I let dpkg
> handle them, even if that they as cruft because people remove instead of
> purge packages.
>
> I do add code to the file under /etc/emacs to check if the package is
> _really_ installed before doing any setup. See for example
> emacs-goodies-el.

Thank you for your response, I've looked now how emacs-goodies-el does
things. It seems that the big difference is that gnus package wants to
install init files only for specific emacs flavors. In detail, I want to
avoid installing gnus package init files for GNU Emacs 23, which
contains newer bundled version of gnus.

(Gnus release policy and versioning is a bit odd, but that shouldn't
matter on this issue.)

Currently gnus package (based on old maintainer scripts) copies init
file to /etc/<flavor>/site-start.d in emacsen-install script instead of
simply letting dpkg install those to generic directory
/etc/emacs/site-start.d.

All this leaves me wondering if the correct solution would be using
/etc/emacs/site-start.d/XXgnus.el but inside it have Emacs version
check, which would skip load-path additions with non-wanted Emacs
versions...

-- 
Tommi Vainikainen