Re: Tramp as ELPA package

[Stefan Monnier]

>> What you can do is create a Tramp package on elpa.git and push releases
>> there (complete with the pre-built auxiliary files).  This is what
>> AUCTeX does, basically (where the files that would ideally be
>> auto-generated during packaging are instead stored in the elpa.git
>> repository after making them manually).
>
> auctex is an external package. We discussed this already, the Tramp
> repository layout does not fit the requirements of a package archive.

I don't see why that makes any difference to my proposition.

I see you misunderstood my suggestion:

> I believe I will upload regularly a generated Tramp package archive to
> <https://ftp.gnu.org/gnu/tramp/elpa>, plus a proper archive-contents
> file, and announe this as Tramp ELPA. Once it is possible to distribute
> Tramp via GNU ELPA I'll switch happily.

Why can't you take that package archive's content, put it in a Git
branch and push that to elpa.git?
The GNU ELPA scripts just take the elpa.git branch and make a tarball
from it, basically, so whatever's in your tarballs can be put in
elpa.git to get the same result.


        Stefan