all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Divya Ranjan <divya@subvertising.org>
To: Ryan Prior <rprior@protonmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: On "next" packages and related confusions.
Date: Tue, 12 Nov 2024 00:50:09 +0000	[thread overview]
Message-ID: <21D166F6-8D68-4288-AE40-F6323DF6DC71@subvertising.org> (raw)
In-Reply-To: <Csrs2fWDqyGqqnNtFV45Y8UwDwCS6Aug3TDpSYJK6TCwk-YGmBHE1hkM3KyHAziAE2e3ThmJSgUL_KyumU7x1vUZAshnr-QtABpxDrYoGsE=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

Hello Ryan,

> 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.

I think the whole "next" category is problematic. Why not just have a version number of that package that's different from the "main" one? So instead of emacs-next have emacs-30.0.9 or whatever. At least here the choice of arbitrariness is visible. A "next" makes no sense.

> 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.

Thank you for this, how can this be added when declaring a package in system or home configuration?

Regards,

Divya Ranjan, Mathematics, Philosophy and Libre Software

[-- Attachment #2: Type: text/html, Size: 943 bytes --]

  reply	other threads:[~2024-11-12  1:02 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.
2024-11-12  0:50   ` Divya Ranjan [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21D166F6-8D68-4288-AE40-F6323DF6DC71@subvertising.org \
    --to=divya@subvertising.org \
    --cc=guix-devel@gnu.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 external index

	https://git.savannah.gnu.org/cgit/guix.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.