Hi Agustin,
Agustin Martin wrote:
> A temporary hack is
[...]
Very interesting (and especially thanks for the reference to
Bug#268466).
I feared the following sequence:
install emacsen-common
install git
remove emacsen-common
remove git
but it actually works fine --- the install/git and remove/git scripts
do not even run unless there is an emacs variant installed, so all
cases seem to be taken care of.
>> Otherwise, I suppose the .el files will
>> have to move to a separate git-emacs package (which would depend on
>> emacsen-common).
>
> If you only add few lisp files I would temporarily use above hack and wait
> for Rob re-design to decide what it allows and what to do.
For now I will be going with a separate git-el package. In general I
don't like the proliferation of tiny packages but in this case it has
some nice side benefits:
- avoids complication on systems that do not want the emacs support;
- gives a chance to point the sysadmin to magit, which she should be
installing instead :);
- gives the elisp scripts a separate package name on the BTS (wow, I
am lazy --- I should be using usertags for that)
Once emacsen-common learns to use triggers, I would like to revisit
this and most likely git-el would be folded back into the main package
then.
Thanks, that was useful.
Jonathan
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
