unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Gottfried <gottfried@posteo.de>
To: help-guix@gnu.org
Subject: add a substitute server and thoughts for improvement
Date: Sun, 10 Apr 2022 09:50:31 +0000	[thread overview]
Message-ID: <fe3d0fc2-49a1-02e9-bc1b-5a6196362ba2@posteo.de> (raw)


Would somebody be so kind and show me this part of his /etc/config.scm

file in order to know where and what I should put there, so that I can

add "bordeaus-guix.gnu.org as a substitute serve?

I checked the manual, but I am not able to do it on my own.


In order not to loose electricity, (which is not good for the 
environment), time (makes a lot of pressure) and hope (guix should 
create hope) when after a "guix package -u" the substitute is not built 
or fails, and my computer has to compile the source, which takes a long 
time,

could not a developer of guix add options:

1. that we are warned about it (that a substitue is not available at the 
moment)
2. that there are options to cancel upgrading one ore more packages
3. that approx. so much time it needs to build the source of a package 
(if that is possible)
4. a question, if I want to use a different substitute server, and if yes
5. an info if on that different substitute server this substitute is 
available,
6. and if not, to cancel this ore more specific package to upgrade.

Guixers could still add other options, which I am not aware of it at the 
moment.

Do guix developers read our questions or do we have to send it to a 
specific email address?

Gottfried






Gottfried


             reply	other threads:[~2022-04-10  9:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10  9:50 Gottfried [this message]
2022-04-11  8:43 ` add a substitute server and thoughts for improvement pelzflorian (Florian Pelz)
  -- strict thread matches above, loose matches on Subject: below --
2022-04-10 18:56 Nathan Dehnel

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=fe3d0fc2-49a1-02e9-bc1b-5a6196362ba2@posteo.de \
    --to=gottfried@posteo.de \
    --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).