Re: [melpa] request: a development TRAMP package (#1179)

[Michael Albinus]

Dave Abrahams <address@hidden> writes:

>     If it's in the Emacs repo, as I suspect, then it won't be going
>     into MELPA, for the same reasons that python.el was removed from
>     MELPA: primarily, that code from Emacs trunk is frequently
>     incompatible with older Emacs versions because it is ruthlessly
>     updated and stripped of backwards-compatibility code.
>
> Makes sense in general. Not sure about this specific case.

For the records, Tramp 2.2.x is still compatible with GNU Emacs 22 and
XEmacs 21.4. This won't change in 2.2.x, and I don't expect to start a
new 2.3 stream this year :-)

According to the remark on *.el.in files: I could imagine to have a
special directory in the Tramp repo with expanded files in this
respect. This directory could be in the usual package format. It would
be rebuild by every git login.

Whether one could ask the package manager to use savannah.gnu.org as
repository I don't know, but this prepared directory could be easy to be
imported into melpa or any other package repository.

>     In general we take that view that if users really want to use the
>     latest versions of libraries included in Emacs HEAD, then they
>     will run Emacs HEAD. That's what I do myself, for ruby-mode and
>     others.

Agreed.

>     Presumably, a month from now this will be moot anyway, because I
>     expect that the faster TRAMP will be in Emacs 24.4.
>     
> That would certainly be nice

I'd expect it rather next spring, but that's based only on my private
crystal ball.

Best regards, Michael.