From: Peter Polidoro <peter@polidoro.io>
To: help-guix@gnu.org
Subject: Guarantee of no broken dependencies?
Date: Fri, 10 Nov 2023 13:37:20 +0100 [thread overview]
Message-ID: <32CCC1D2-D832-484F-84CF-B5ABA6EA2C2B@polidoro.io> (raw)
For every commit to the Guix master branch, is there a guarantee that there are no packages with broken dependencies?
I have not experienced packages with broken dependencies, so I am curious how that is checked. In theory, someone could make a commit that accidentally breaks other packages correct? Aren’t most inputs just found by name, not name and version or hash?
Do packages not get broken, though, because right before every commit the updated package is built, along with every package that depends on the updated package? Is that enough to make sure all dependencies are fine? There are no race conditions with other people making updates at the same time?
How can we do such a consistency check or have such a guarantee when we use multiple channels? Does we just rebuild every package in every non-Guix channel every time we update Guix to find out what breaks?
next reply other threads:[~2023-11-10 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 12:37 Peter Polidoro [this message]
2023-11-10 14:00 ` Guarantee of no broken dependencies? Ignas Lapėnas
2023-11-10 14:22 ` Maxim Cournoyer
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=32CCC1D2-D832-484F-84CF-B5ABA6EA2C2B@polidoro.io \
--to=peter@polidoro.io \
--cc=help-guix@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.
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).