From: Alyssa Ross <hi@alyssa.is>
To: Michael Raskin <7c6f434c@mail.ru>
Cc: devel@spectrum-os.org
Subject: [spectrum-devel] Re: [PATCH www] design: state subdirectories, not block devices
Date: Fri, 18 Oct 2019 18:56:59 +0000 [thread overview]
Message-ID: <8736fpanlw.fsf@alyssa.is> (raw)
In-Reply-To: <E1iL4U3-0003so-RW.7c6f434c-mail-ru@smtp17.mail.ru>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
>>> Also, I might want to use some binary cache, but when I am offline Nix
>>> builds wait for a long time for a reply from a binary cache. It's not so
>>> bad if I am intentionally building something and can pass an empty value
>>> for binary-caches via the command line, but doing it for each new
>>> command I execute sounds excessive.
>>
>>Yes, this is true, although I consider it a Nix bug. I shouldn't have
>>to remember to say --option substitute false for trivial offline
>>rebuilds.
>
> But there are cases where it would be hard for Nix to get right (the
> ??network won't become reachable?? part ??? the notion of triviality of the
> build is obviously hopeless even with manual declaration)
IMO it should start builds in parallel with trying to pull them from the
network. It can abort the other after one finishes. But that's OT.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-10-18 18:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 20:28 [spectrum-devel] " Alyssa Ross
2019-10-16 21:33 ` Michael Raskin
2019-10-16 23:15 ` [spectrum-devel] " Alyssa Ross
2019-10-17 7:47 ` Michael Raskin
2019-10-17 11:36 ` Alyssa Ross
2019-10-17 12:09 ` Michael Raskin
2019-10-18 18:51 ` Alyssa Ross
2019-10-18 18:56 ` Alyssa Ross [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=8736fpanlw.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=7c6f434c@mail.ru \
--cc=devel@spectrum-os.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 public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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 NNTP newsgroup(s).