From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] emacs 28.1-1 (TEST)
Date: Wed, 13 Apr 2022 08:17:47 -0400 [thread overview]
Message-ID: <f3325468-ac0a-ea18-8983-d8a9ba376b0d@cornell.edu> (raw)
In-Reply-To: <announce.6d19e281-0d11-97e9-c5f9-67dc4d6693d5@cornell.edu>
On 4/6/2022 9:04 AM, Ken Brown via Cygwin-announce wrote:
> The following packages have been uploaded to the Cygwin distribution as test
> releases. Note that there have been some packaging changes, so that the package
> names better reflect the package contents.
>
> * emacs-28.1-1
>
> This is now a virtual package that forces installation of one of the following
> four "binary" packages. If you don't select one of these four, then emacs-basic
> will be installed by default.
>
> * emacs-basic-28.1-1
> * emacs-w32-28.1-1
> * emacs-gtk-28.1-1
> * emacs-lucid-28.1-1
>
> Each of these contains an emacs binary of the same name as the package. For
> example, emacs-basic provides /usr/bin/emacs-basic.exe, formerly called
> emacs-nox.exe. emacs-gtk used to be called emacs-X11. For backwards
> compatibility, the old names /usr/bin/emacs-nox and /usr/bin/emacs-X11 can still
> be used.
>
> * emacs-common-28.1-1
>
> This contains files needed by each of the four binaries.
>
> Emacs is a powerful, customizable, self-documenting, modeless text editor. Emacs
> contains special code editing features, a scripting language (elisp), and the
> capability to read mail, news, and more without leaving the editor.
>
> This is an update to the latest upstream release. Browse the NEWS file ('C-h n'
> within emacs) for changes since the last release.
>
> This release is a test release only because of the packaging changes. If no
> problems are reported, it will be promoted from test to current in a week or so.
This has now been promoted to current.
> Unlike the previous test release, this release was *not* built with the new
> native compilation feature, which still needs more testing. Once 28.1-1 has
> been promoted to current, I will make a new test release, 28.1-2, built with
> native compilation.
I'll do this within the next few days, once I'm sure there are no glitches with
the new packaging.
Ken
prev parent reply other threads:[~2022-04-13 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 13:04 Ken Brown via Cygwin-announce
2022-04-13 12:17 ` Ken Brown [this message]
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=f3325468-ac0a-ea18-8983-d8a9ba376b0d@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).