From: "Simen Endsjø" <contact@simendsjo.me>
To: help-guix@gnu.org
Subject: Avoid sending sources to offload servers
Date: Thu, 07 Nov 2024 09:57:26 +0100 [thread overview]
Message-ID: <bf28f4b0-8e2c-4360-b8af-b9a26cb2e2b1@app.fastmail.com> (raw)
I notice package sources are sent to offload servers. I have a build that has
1.9GB sources, and results in a 4.7GB store item. I would have thought only the
definitions were sent to the build machine, and it would download the 1.9GB
file, but it seems this file is sent from my machine. I cannot see a way around
this, and it makes it difficult to combine this package with packages I wish to
offload as I cannot state certain packages shouldn't be offloaded.
Not sure what I'm asking here, just wanted to point out an issue which causes
problems.
next reply other threads:[~2024-11-07 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 8:57 Simen Endsjø [this message]
2024-11-07 9:14 ` Avoid sending sources to offload servers Hilton Chain
2024-11-07 10:07 ` Simen Endsjø
2024-11-07 11:00 ` Edouard Klein
2024-11-07 11:08 ` Simen Endsjø
2024-11-08 20:55 ` Tomas Volf
2024-11-08 21:08 ` Simen Endsjø
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=bf28f4b0-8e2c-4360-b8af-b9a26cb2e2b1@app.fastmail.com \
--to=contact@simendsjo.me \
--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).