From: Ryan Prior via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: "divya@subvertising.org" <divya@subvertising.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: On "next" packages and related confusions.
Date: Mon, 11 Nov 2024 16:46:22 +0000 [thread overview]
Message-ID: <Csrs2fWDqyGqqnNtFV45Y8UwDwCS6Aug3TDpSYJK6TCwk-YGmBHE1hkM3KyHAziAE2e3ThmJSgUL_KyumU7x1vUZAshnr-QtABpxDrYoGsE=@protonmail.com> (raw)
In-Reply-To: <87pln1ztz6.fsf@subvertising.org>
-------- Original Message --------
On 11/11/24 9:10 AM, Divya Ranjan <divya@subvertising.org> wrote:
> 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?
As your intuition hints, "next" is arbitrary. It indicates somebody's judgement that it would be inappropriate to update the main package to that version, perhaps because of instability or perhaps because the update would require a lot of rebuilds.
I think it would be appropriate if each "next" package had a code comment, or perhaps an addendum to its package description, describing how it relates to the main packaged version.
In case you don't know about "--with-latest", that's the supported way to install the latest master branch of a package. "-next" packages are not meant to closely track master.
next prev parent reply other threads:[~2024-11-11 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 15:10 On "next" packages and related confusions Divya Ranjan
2024-11-11 16:46 ` Ryan Prior via Development of GNU Guix and the GNU System distribution. [this message]
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='Csrs2fWDqyGqqnNtFV45Y8UwDwCS6Aug3TDpSYJK6TCwk-YGmBHE1hkM3KyHAziAE2e3ThmJSgUL_KyumU7x1vUZAshnr-QtABpxDrYoGsE=@protonmail.com' \
--to=guix-devel@gnu.org \
--cc=divya@subvertising.org \
--cc=rprior@protonmail.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.
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).