From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: divya@subvertising.org
Cc: guix-devel@gnu.org
Subject: On the "next" packages, and packaging confusion.
Date: Sat, 23 Nov 2024 15:34:24 +0000 [thread overview]
Message-ID: <87a5dqnev3.fsf@gmail.com> (raw)
In-Reply-To: 87o72ml57j.fsf@subvertising.org
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
Hi Divya,
Speaking from Python/Golang/Astro teams perspective.
I see and use *-next where I need the latest package version but
updating inherited one would trigger a large amount of re-builds. It may
be swap on dedicated team branch when more packages start needing it.
In Golang, there are breaking changes versions which are specified in
module path and reflected in Guix' package names e.g.
go-github-com-<owner>-<project>-v2
If updating package does not trigger more than 300-400 related packages
there is not need to introduce *-next variant and it's reasonable just to
update to the latest version.
Hope it helps
Live well!
--
Oleg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2024-11-23 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 15:34 Sharlatan Hellseher [this message]
2024-11-23 15:53 ` On the "next" packages, and packaging confusion Divya Ranjan
-- strict thread matches above, loose matches on Subject: below --
2024-11-22 23:57 Christopher Howard
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=87a5dqnev3.fsf@gmail.com \
--to=sharlatanus@gmail.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).