Re: Best practice for tracking current release?

[Ben Hyde]

On 13 Sep 2015, at 12:08, Michael Albinus wrote:
> "Ben Hyde" <address@hidden> writes:
>
> Hi Ben,
>
> > What’s “best practice” for staying in sync with the current 
> > release? -
> > ben
> >
> > ps. My tramp is 2.2.9-24.4, and it has one particularly frustrating
> > behavior (sometimes it won’t save files (complaining “byte-code: 
> > Wrong
> > type argument: stringp, (nil)”).  I notice[1] that the latest 
> > verison
> > appears to be 2.2.12, but tramp’s not in the enumeration shown by 
> > M-x
> > package-list-packages.
>
> Tramp is not distributed via ELPA. So you must download the tar-file,
> and perform the traditional triple jump "./configure; make; make 
> install".
>
> See <http://www.gnu.org/software/tramp/#Installation>.
>
> > pps. Thanks, I don’t know how I’d work without Tramp!
>
> Thanks, same here :-)
>
> Best regards, Michael.

Thank you.

Meanwhile, if el-get is setup you can ask it to do the classic song and 
dance.

    M-x el-get-install
         and ask for tramp.

You may want to edit tramp’s el-get recipe (el-get/recipes/tramp.rcp) 
to get a
stable release, if so add:

   :branch “V-2-2-12”

 - ben