|
From: | GNU bug Tracking System |
Subject: | [debbugs-tracker] bug#32022: closed ((new feature) Change guix pull to choose commits for which substitutes is already built by default ) |
Date: | Mon, 17 Dec 2018 10:54:01 +0000 |
Your message dated Mon, 17 Dec 2018 02:53:29 -0800 with message-id <address@hidden> and subject line bug#32022: (new feature) Change guix pull to choose commits for which substitutes is already built by default has caused the debbugs.gnu.org bug report #32022, regarding (new feature) Change guix pull to choose commits for which substitutes is already built by default to be marked as done. (If you believe you have received this mail in error, please contact address@hidden) -- 32022: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32022 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: (new feature) Change guix pull to choose commits for which substitutes is already built by default Hi Date: Sat, 30 Jun 2018 21:06:55 +0200
I would like it to be easy for newcomers to do the right thing when pulling.
I suggest we by default give guix pullers a bit more information and interaction.
Something like this:
"Checking for newly built derivations of guix at hydra.gnu.org...
(table)
Date Commit Succeeded for x64?
28/6 54d84d8 yes
...
...
...
Pulling based on default commit selection scheme (see --help for details)
Most recently built commit is x4678x85 built x hours ago.
Continuing in 10 seconds...
Press ctrl+c to abort. "
Guix pull gets a new argument " -d" allowing you to specify the days old commit you want to select.
E. G. Guix pull -d 5 selects a commit build successfully 5 days ago by hydra.
Guix weather could show the table only, if the argument --guix-pull was given.
--
Cheers Swedebugia
--- End Message ---
--- Begin Message ---Subject: bug#32022: (new feature) Change guix pull to choose commits for which substitutes is already built by default Date: Mon, 17 Dec 2018 02:53:29 -0800 Closed as we now have channels and ludo' had good arguments for why to not implement my suggestion.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |