From: Fis Trivial <ybbs.daans@hotmail.com>
To: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Is it necessary to download the native inputs while installing packages?
Date: Thu, 18 Jan 2018 15:19:18 +0000 [thread overview]
Message-ID: <MWHPR16MB0063566105D780A118359D7992E80@MWHPR16MB0063.namprd16.prod.outlook.com> (raw)
The network connections to hydra is bad at day time from where I am, the
download speed is about 10kB/s, I can only work with guix at night.
And sometimes I use guix --fallback option(like texlive), guix will redirect to
the upstream download link. Chances are the upstream has even worse network
bandwidth, then I have to manually find a mirror of that particular upstream
and use `guix download`.
In the case of *texlive-texmf*, it serves mostly as a build dependence. To make
things even less convenient, most of the mirror site only store its ISO
package, not the tar ball used in guix package.
So, I gotta wonder, can we just download the normal inputs and propagated
inputs from hydra while installing packages? Would that break something like
the functional property of guix?
next reply other threads:[~2018-01-18 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 15:19 Fis Trivial [this message]
2018-01-18 17:36 ` Is it necessary to download the native inputs while installing packages? Tobias Geerinckx-Rice
2018-01-18 19:56 ` Leo Famulari
2018-01-18 20:01 ` Tobias Geerinckx-Rice
2018-01-18 20:54 ` Fis Trivial
2018-01-19 13:24 ` Ludovic Courtès
2018-01-20 0:13 ` Leo Famulari
2018-01-20 10:40 ` Prevent native-inputs references ending up in the final binary Danny Milosavljevic
2018-01-20 15:47 ` Tobias Geerinckx-Rice
2018-01-21 22:37 ` Leo Famulari
2018-01-21 22:47 ` Tobias Geerinckx-Rice
2018-01-24 14:26 ` Ludovic Courtès
2018-01-26 0:56 ` Fis Trivial
2018-01-26 1:05 ` Tobias Geerinckx-Rice
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=MWHPR16MB0063566105D780A118359D7992E80@MWHPR16MB0063.namprd16.prod.outlook.com \
--to=ybbs.daans@hotmail.com \
--cc=guix-devel@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.