Re: Magit

[Philip Kaludercic]

Akib Azmain Turja <akib@disroot.org> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>
>>> Actually, in a sense it's pretty easy: just make an exception for the
>>> rule that all code needs to have its copyright assigned to the FSF.
>>
>> Sounds good to me, FWIW.
>>
>>> But even if we do make such an exception, having a copy of Magit in
>>> `emacs.git` would add extra maintenance burden to keep that copy in sync
>>> with the one maintained elsewhere.  So for administrative reasons, it's
>>> probably preferable to keep it outside of `emacs.git`.
>>
>> I'm not sure I understand the objection.  Is it not just a question of
>> popping something like this in a shell script that runs every N days:
>>
>>   git clone <MAGIT-URL> magit
>>   cp magit/*.el lisp/magit
>>   rm -rf magit
>>   git commit -a -m "; Auto-update Magit"
>>   git push
>
> Yeah, I also think it isn't a too big problem.  I also think we should
> take the portable packages (i.e. the packages which don't depend on
> Emacs internals, e.g. term, artist, comint (maybe), doctor) out of the
> main Emacs repository and make them available through GNU ELPA (while
> still keeping a copy in main Emacs repository).  That way Emacs 28.1
> users (and possibly Emacs 27.2 users) will get the latest updates to
> those packages.
>
>>
>> If we want to be a bit more conservative, we have code in NonGNU ELPA to
>> check out the latest tagged package version.
>
> The last time I checked, the Magit version hosted on NonGNU ELPA was
> completely broken.

I've been using the version from NonGNU ELPA since it has been added
(last year), and there haven't been any issues.