From: kiasoc5@disroot.org
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Repology and outdated packages
Date: Thu, 09 Jun 2022 04:05:35 +0000 [thread overview]
Message-ID: <de097ed381a1a67aa81cafe515f2b9d7a3733dd8@disroot.org> (raw)
In-Reply-To: f563cd29cc2130f0aa54c2eeb139a5bddd8e98ff@disroot.org
June 8, 2022 at 9:38 PM, "Ludovic Courtès" <ludo@gnu.org mailto:ludo@gnu.org?to=%22Ludovic%20Court%C3%A8s%22%20%3Cludo%40gnu.org%3E > wrote:
> Guix is *potentially* even more up-to-date than NixOS thanks to
> ‘--with-latest’ and ‘--with-branch’! \o/
I do use --with-latest for testing package upgrades. But it is tedious to type
$ guix build X --with-latest=X
in order to test the latest package.
What would be nice is if
$ guix build --latest X
is an equivalent command. Certainly a shell script could take care of that:
guix-build-with-latest() {
guix build "$1" --with-latest="$1"
}
but having it done in guix itself would be convenient.
> Seriously though, we could take better advantage of the tooling that we
> have: ‘guix refresh’, ‘guix graph’, and the corresponding APIs. With
> that, we can write code that automatically tries out package updates and
> prepares patches, for instance. We could even largely automate “update
> trains” (what we’re doing with master/staging/core-updates).
It could be an option to guix refresh, for example
$ guix build --latest X --export-patch
would build X with the latest version and export a patch with an appropriate commit message (like marking failed builds with DRAFT). This would help users contribute without having to clone the git repo.
prev parent reply other threads:[~2022-06-09 4:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 18:39 Repology and outdated packages kiasoc5
2022-06-07 18:47 ` Nicolas Goaziou
2022-08-11 22:46 ` Vagrant Cascadian
2022-08-14 2:32 ` Maxim Cournoyer
2022-06-07 21:32 ` Maxime Devos
2022-06-09 8:02 ` Maxime Devos
2022-06-07 21:41 ` Maxime Devos
2022-06-08 21:38 ` Ludovic Courtès
2022-06-09 3:07 ` Oleg Pykhalov
2022-06-09 3:49 ` kiasoc5
2022-06-09 4:05 ` kiasoc5 [this message]
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=de097ed381a1a67aa81cafe515f2b9d7a3733dd8@disroot.org \
--to=kiasoc5@disroot.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.