From: Divya Ranjan <divya@subvertising.org>
To: guix-devel@gnu.org
Subject: On "next" packages and related confusions.
Date: Mon, 11 Nov 2024 15:10:53 +0000 [thread overview]
Message-ID: <87pln1ztz6.fsf@subvertising.org> (raw)
Hello,
As someone who’s been recently involved in packaging some software for GNU Guix I’m confused with certain choices, mostly with the [package]-next category. What should these next packages be? "More recent" than the non-next package? If so, how much more recent? One release ahead? Or is it supposed to follow the latest master release from the source repository of the package, and the non-next package would be the stable one?
None of the above options seem to satisfy, emacs-next does not follow the latest master, but it further away than one release from the stable. So what exactly does emacs-next follow for being updated? This is not only confusing, but I believe creating issues in packaging as well, someone has even consdiered packaging a "emacs-nextnext" [0].
A better solution is necessary, at least if not that we should decide what and how should the "next" packages be provided and packaged, emacs-next doesn’t even have a description. The next packages should have a _distinct_ description from the non-next ones, so that when the user is installing it they know that they’re installing not a stable, or more recent or whatever we decide as the distinguishing element between the two categories.
I’ve seen similar issues in trying to upgrade the ghc package as well, the ghc-next isn’t clear as to what its following [1].
A clearance of these confusions would be better for both package maintainers and end-users who don’t see much beyond the description, version and do `guix install'.
[1]: https://issues.guix.gnu.org/issue/47335
[0]: https://issues.guix.gnu.org/73281
Regards,
--
Divya Ranjan,
Philosophy, Mathematics, Libre Software.
next reply other threads:[~2024-11-11 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 15:10 Divya Ranjan [this message]
2024-11-11 16:46 ` On "next" packages and related confusions Ryan Prior via Development of GNU Guix and the GNU System distribution.
2024-11-12 0:50 ` Divya Ranjan
2024-11-12 1:21 ` Philip McGrath
2024-11-12 12:21 ` Divya Ranjan
2024-11-12 18:00 ` Simon Tournier
2024-11-12 19:25 ` Liliana Marie Prikler
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=87pln1ztz6.fsf@subvertising.org \
--to=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).