[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [AUCTeX-devel] auctex pkg uptodate?

From: Tassilo Horn
Subject: Re: [AUCTeX-devel] auctex pkg uptodate?
Date: Sat, 19 Jul 2014 10:22:40 +0200
User-agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/24.4.50 (gnu/linux)

Uwe Brauer <address@hidden> writes:

Hi Uwe,

>    >> The reason why I am asking this, is the fact that I am now convinced
>    >> that 11.87 has some important improvement over 11.84
>    > We very much hope so!  And the git head has many improvements over
>    > 11.87, too.
> Now I am confused. You just stated that they are only bug fixes now
> you say that git head has "many improvements" ok one could interpret
> bug fix as improvement but this is really what you mean???

No, ELPA is just 11.87 + several fixes.  The Git version is the bleeding

>    > Out of couriosity, what's the hurdle/difference of our official
>    > AUCTeX XEmacs package and the official XEmacs AUCTeX package in the
>    > XEmacs package repo?
> This is a long and sad story, subject to many flamewars between
> David Karstrup and Steve Turnbull, better let us drop the
> subject.

Ok, I see.

>    > I can understand that, but I have nothing to offer. You
>    > could just grab the 11.87 release and patch it with the
>    > fixes and enhancements you like. Or as said above, wait for
>    > 11.88, but of course that will be released From the git
>    > head, so more testing effort on your side.
> Right, any time schedule for 11.88?

Basically, now would be fine with me.  What's currently missing is
someone who is able to build the windows package.  I hope that Ralf
reads this anytime soon.

>    > Surely, no.  In an ideal world, I'd simply drop all compatibility, all
>    > the build complexity, and simply develop AUCTeX in the ELPA repo (or
>    > keep the ELPA AUCTeX branch in strict sync with the AUCTeX git repo),
>    > and only do ELPA releases.  For users, that's by far the easiest and
>    > fool-proof way of getting AUCTeX, and for us maintainers, that's the
>    > easiest way to cut new releases.
>    > Now of course, that would exclude XEmacs and users of older emacsen, so
>    > that's not realistic for now.  But it would suit me as a maintainer who
>    > favors releasing frequently, preferably after every single fixed bug and
>    > every new feature.
> Please don't exclude xemacs, realistically now I have nothing to
> offer than a polite request.

No, I won't, at least not deliberatly. ;-)


Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]