From: Christopher Howard <christopher@librehacker.com>
To: Divya Ranjan via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org>
Cc: Divya Ranjan <divya@subvertising.org>
Subject: Re: On the "next" packages, and packaging confusion.
Date: Fri, 22 Nov 2024 14:57:45 -0900 [thread overview]
Message-ID: <875xoevn2e.fsf@librehacker.com> (raw)
In-Reply-To: Divya Ranjan via's message of "Mon, 11 Nov 2024 05:17:20 +0000 (1 week, 4 days, 18 hours ago)"
Hi, I'm not a Guix maintainer, but just thought I would mention that, regarding Emacs:
- There is an official, distinct branch for the next release (in this case, Emacs 30)
- They do have official "pre-test" releases, in the year before the release, which in this case were 30.0.91 and 30.0.92.
- Before that, i.e., before the pre-test releases, it appeared that guix was camping on 30.0.50 (or was it 51)?. I was fine with that, because the important thing (to me) is that the guix package emacs-next could provides a package definition that I could use (with shell -D) to build any commit in the 30 branch. I'm not sure, off-hand, how 30.0.50 was picked exactly.
So, for me at least, the important thing is that emacs-next is taken from the branch for the next release. And if it gets adjusted at the time the pre-tests are release, that is also nice.
--
Christopher Howard
next reply other threads:[~2024-11-22 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 23:57 Christopher Howard [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-23 15:34 On the "next" packages, and packaging confusion Sharlatan Hellseher
2024-11-23 15:53 ` Divya Ranjan
2024-11-11 5:17 Divya Ranjan via Development of GNU Guix and the GNU System distribution.
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xoevn2e.fsf@librehacker.com \
--to=christopher@librehacker.com \
--cc=divya@subvertising.org \
--cc=guix-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).