From: Quiliro <quiliro@riseup.net>
To: help-guix@gnu.org
Subject: Re: persistent reproducibility ?
Date: Fri, 24 Mar 2017 07:05:18 -0500 [thread overview]
Message-ID: <20170324070518.79db8c99@riseup.net> (raw)
In-Reply-To: <87d1d7cjx3.fsf@gmail.com>
El Thu, 23 Mar 2017 22:39:52 -0700
Chris Marusich <cmmarusich@gmail.com> escribió:
> By the way, in case you were wondering, one reason why we don't put
> the sources for every package into the Guix source tree is because
> that would make the Guix source tree prohibitively large. The
> transitive closure of sources for GNU Hello alone weighs in at 1750
> MiB (wow!) when uncompressed. And that's only for those specific
> versions of the source files.
How much space would the sources for every package in compressed
format take?
--
Example of rude top posting:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I leave quotations after my reply?
Saluton,
Quiliro
0987631031
next prev parent reply other threads:[~2017-03-24 12:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 11:15 persistent reproducibility ? zimoun
2017-03-21 14:49 ` Alex Sassmannshausen
2017-03-21 16:19 ` Ludovic Courtès
2017-03-22 17:39 ` zimoun
2017-03-23 8:44 ` Alex Sassmannshausen
2017-03-23 15:33 ` zimoun
2017-03-23 12:32 ` Ricardo Wurmus
2017-03-23 16:46 ` zimoun
2017-03-24 15:45 ` Ludovic Courtès
2017-03-25 13:07 ` zimoun
2017-03-24 5:39 ` Chris Marusich
2017-03-24 12:05 ` Quiliro [this message]
2017-03-26 9:39 ` Chris Marusich
2017-03-26 15:03 ` Quiliro
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=20170324070518.79db8c99@riseup.net \
--to=quiliro@riseup.net \
--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).