From: Carsten Mattner <carstenmattner@googlemail.com>
To: Eric Schulte <eric.schulte@gmx.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
monnier@iro.umontreal.ca, Drew Adams <drew.adams@oracle.com>,
emacs-devel@gnu.org
Subject: Re: Periodical releases
Date: Mon, 2 Jan 2012 22:31:13 +0100 [thread overview]
Message-ID: <CACY+HvoWCK3GgZ_KqkgvRHnpLgfmjVESWpqxhUQoaKx-2M=nXA@mail.gmail.com> (raw)
In-Reply-To: <87wr9997bz.fsf@gmx.com>
On Mon, Jan 2, 2012 at 9:29 PM, Eric Schulte <eric.schulte@gmx.com> wrote:
>>> I would have less of a need to build emacs manually if
>>> there were more release and therefore standard emacs
>>> Linux distros was more up to date.
>>
>> The problem you raise here is apparently one of the difficulty/nuisance of
>> building Emacs. It is not about how often to publish releases.
>>
>> Publishing non-release MS Windows binaries periodically has been _very_ helpful
>> (thank you again to those who have created and posted the builds). At least on
>> that platform, that is a solution to the problem you raise.
>>
>
> It seems that the fix here is not to change the Emacs development and
> release process, but rather to encourage package maintainers to provide
> packages tracking the Emacs trunk. The debian emacs-snapshot package
> described as "The GNU Emacs editor (development snapshot)" returns the
> following which is certainly many months (maybe years?) out of date.
>
> $ emacs --version
> GNU Emacs 23.2.1
This is one of the things which I always hoped Gentoo, Exherbo or rPath
would solve. Of those Gentoo and Exherbo seem to be the most likely
solution.
Fedora stable is a good way to get current software while not having
to rely on Debian sid.
Debian has the advantage of doko releasing gcc-snapshot regularly
as a nice way to check for future warnings in unreleased gcc versions.
next prev parent reply other threads:[~2012-01-02 21:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 12:00 Periodical releases Carsten Mattner
2012-01-01 22:41 ` Stefan Monnier
2012-01-02 10:40 ` Carsten Mattner
2012-01-02 11:36 ` Eli Zaretskii
2012-01-02 12:57 ` Carsten Mattner
2012-01-02 17:31 ` Eli Zaretskii
2012-01-02 19:05 ` Drew Adams
2012-01-02 19:54 ` chad
2012-01-02 21:36 ` Carsten Mattner
2012-01-02 20:29 ` Eric Schulte
2012-01-02 21:31 ` Carsten Mattner [this message]
2012-01-02 20:41 ` Lluís
2012-01-02 21:23 ` Carsten Mattner
2012-01-02 22:14 ` Drew Adams
2012-01-02 22:27 ` Carsten Mattner
2012-01-05 2:34 ` Dave Abrahams
2012-01-05 2:58 ` Chong Yidong
2012-01-05 3:36 ` Dave Abrahams
2012-01-05 4:23 ` Óscar Fuentes
2012-01-05 13:25 ` Eli Zaretskii
2012-01-05 13:41 ` Dave Abrahams
2012-01-05 9:31 ` Bastien
2012-01-05 10:11 ` Leo
2012-01-05 11:31 ` Carsten Mattner
2012-01-05 12:56 ` Jambunathan K
2012-01-05 14:00 ` Leo
2012-01-05 14:30 ` Jambunathan K
2012-01-05 11:28 ` Carsten Mattner
2012-01-05 14:18 ` Eric Schulte
2012-01-05 11:33 ` Carsten Mattner
2012-01-05 5:43 ` Eli Zaretskii
2012-01-05 12:20 ` Dave Abrahams
2012-01-05 15:34 ` Drew Adams
2012-01-03 22:23 ` Stefan Monnier
2012-01-03 18:18 ` What's in a feature? (was: Periodical releases) Bastien
2012-01-04 3:24 ` Stephen J. Turnbull
2012-01-04 10:03 ` What's in a feature? Bastien
2012-01-04 12:43 ` Juanma Barranquero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACY+HvoWCK3GgZ_KqkgvRHnpLgfmjVESWpqxhUQoaKx-2M=nXA@mail.gmail.com' \
--to=carstenmattner@googlemail.com \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=eric.schulte@gmx.com \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.