[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tramp as ELPA package
From: |
Stephen Leake |
Subject: |
Re: Tramp as ELPA package |
Date: |
Sat, 06 Apr 2019 16:17:13 -0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (windows-nt) |
Michael Albinus <address@hidden> writes:
> Stephen Leake <address@hidden> writes:
>
>> If people edit ada-mode in elpa, I have to copy the edits back to my
>> devel tree; I suspect that is Michael's main complaint. Uploading a
>> package archive to elpa, rather than source files, prevents that.
>
> Yes.
>
>> That seems like a reasonable work flow. It does violate the principle
>> that elpa packages be editable by emacs maintainers; they are reduced to
>> deleting the package if they see a serious problem (as opposed to fixing
>> the problem).
>
> Tramp lives also in Emacs' master, so that problem looks less hurting
> for Tramp.
There's supposed to be a way to take code in Emacs git master and make
it an ELPA package automatically (a "core ELPA package"); is that
working yet? Or is the other way around? Either way, there should be
only one copy, either in emacs git master or elpa git master.
--
-- Stephe
- Re: Tramp as ELPA package, Michael Albinus, 2019/04/04
- Re: Tramp as ELPA package, Stefan Monnier, 2019/04/04
- Re: Tramp as ELPA package, Stephen Leake, 2019/04/05
- Re: Tramp as ELPA package, Stephen Leake, 2019/04/05
- Re: Tramp as ELPA package, Michael Albinus, 2019/04/05
- Re: Tramp as ELPA package,
Stephen Leake <=
- Re: Tramp as ELPA package, Michael Albinus, 2019/04/07
- Re: Tramp as ELPA package, Stefan Monnier, 2019/04/06
- Re: Tramp as ELPA package, Michael Albinus, 2019/04/08
- Re: Tramp as ELPA package, Stefan Monnier, 2019/04/08
- Re: Tramp as ELPA package, Michael Albinus, 2019/04/08
- Re: Tramp as ELPA package, Stefan Monnier, 2019/04/08
Re: Tramp as ELPA package, Achim Gratz, 2019/04/05