From: Ryan Prior <firstname.lastname@example.org> To: zimoun <email@example.com>, "Ludovic Courtès" <firstname.lastname@example.org>, "Development of GNU Guix and the GNU System distribution" <email@example.com>, "Pierre Neidhardt" <firstname.lastname@example.org> Subject: Re: GNU Guix 1.2.0rc2 available for testing! Date: Fri, 20 Nov 2020 03:13:19 +0000 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> [-- Attachment #1: Type: text/plain, Size: 974 bytes --] On November 19, 2020, Pierre Neidhardt <email@example.com> wrote: > [--without-tests] would encourage untested builds if I > recall correctly That may have been a concern (I wasn't part of the conversation) but I don't see how the current implementation could do that. If a normal "guix build foo" fails, then it's a busted package period. I'm glad for the "without-tests" option because when I'm working on packages with a test suite that takes more than a few seconds, I like to make sure that the rest of everything is working before I start running the tests. Another thing I'd like is an option to build a package reusing the state from a previous build. If a package I'm working on takes a minute or longer to build and I'm having some sort of difficulty, it's obnoxious to wait for that to complete again after every cycle. It could be near instantaneous if I could re-use a cached build, which is doable in Docker, Earthly, and other containerized build systems. [-- Attachment #2: Type: text/html, Size: 3305 bytes --]
next prev parent reply other threads:[~2020-11-20 3:14 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-18 18:53 Ludovic Courtès 2020-11-19 2:24 ` zimoun 2020-11-19 8:34 ` Pierre Neidhardt 2020-11-20 3:13 ` Ryan Prior [this message] 2020-11-20 9:34 ` Pierre Neidhardt 2020-11-22 2:53 ` Maxim Cournoyer 2020-11-20 9:23 ` zimoun 2020-11-20 11:25 ` Ludovic Courtès
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: GNU Guix 1.2.0rc2 available for testing'\!'' \ /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
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 NNTP newsgroup(s).