From: Simon Tournier <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guix-devel@gnu.org
Subject: Re: "guix pack -f docker" does too much work
Date: Thu, 26 Sep 2024 18:18:51 +0200 [thread overview]
Message-ID: <87ploqjslw.fsf@gmail.com> (raw)
In-Reply-To: <87o74q3wwh.fsf@elephly.net>
Hi,
On Sat, 14 Sep 2024 at 20:36, Ricardo Wurmus <rekado@elephly.net> wrote:
>> In past discussions (such as the implementation of the 'RPM' pack
>> format) we had concluded that a single derivation was preferable. Large
>> chunks to be sent to offload machines over the network are not very
>> practical, and as Ludovic said, they also require more store space.
Well, the argument “require more store space” appears to me as an
“half-joke”when you know all the space that is required by Guix for a
day-to-day usage. :-) I don’t buy it. ;-)
About offload, indeed. And this can be a “bad surprise”.
> Dependent on the situation I can see one approach to be preferrable to
> the other, and in other situations this could very well be reversed.
I agree.
> Can we expose this choice to the command line interface of "guix pack"?
Maybe the switch could be with the option ’--no-offload’ instead of
adding yet another one.
Cheers,
simon
next prev parent reply other threads:[~2024-10-03 11:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 12:58 "guix pack -f docker" does too much work Ricardo Wurmus
2024-05-30 13:10 ` Michal Atlas
2024-06-17 11:21 ` Ludovic Courtès
2024-06-17 11:57 ` Michal Atlas
2024-06-17 21:24 ` Ludovic Courtès
2024-06-01 13:58 ` Ludovic Courtès
2024-06-01 19:07 ` Ricardo Wurmus
2024-06-03 7:09 ` Andy Wingo
2024-06-04 18:14 ` Simon Tournier
2024-09-14 14:55 ` Maxim Cournoyer
2024-09-14 18:36 ` Ricardo Wurmus
2024-09-15 0:42 ` Suhail Singh
2024-09-26 16:18 ` Simon Tournier [this message]
2024-10-05 14:01 ` Maxim Cournoyer
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=87ploqjslw.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=rekado@elephly.net \
/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.