From: Simon Tournier <zimon.toutoune@gmail.com>
To: wolf <wolf@wolfsden.cz>, Yasuaki Kudo <yasu@yasuaki.com>
Cc: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
help-guix <help-guix@gnu.org>
Subject: Re: VSCode DevContainer for Guix? (Yasuaki Kudo)
Date: Wed, 23 Aug 2023 17:12:51 +0200 [thread overview]
Message-ID: <868ra13i8c.fsf@gmail.com> (raw)
In-Reply-To: <ZK5j1_4qrfG27Dcn@ws>
Hi,
On Wed, 12 Jul 2023 at 10:27, wolf <wolf@wolfsden.cz> wrote:
>> Then, it will create a Docker image as an artifact from the CI-run.
>> The image is as small as it can be because Guix only installs the
>> necessary software.
>
> Careful about this assumption, Guix-generated container images are pretty large
> and include a lot of things you might not want in there (man, info pages, bash,
> ...). I am not saying "do not use it", but if you try to convince people to use
> Guix for container builds, size should not be your argument (especially since
> Alpine exists as an alternative).
Yes, the images generated by Guix cannot considered as minimal. :-)
Aside bugs – see #63050 [a] for one example of such bug –, as I pointed
in [b],
The tacit policy with Guix packages is that the packages are usually by
default “feature maximalist” or specifically named « <foo>-minimal » …
> Right, and reportedly, Alpine-based images for things like Python are
> smaller than what we do. There’s no cheating here: images are
> self-contained.
…contrary to Alpine where the packages are usually by default “feature
minimalist” or specifically named « <foo>-<with-feature> ».
Consider the package Emacs [1] and give a look at the recipe for the
package named ’emacs’ [2]. Well, this Alpine package ’emacs’ looks like
the Guix package named ’emacs-minimal’, and then Alpine provides these
variants (subpackages):
emacs-doc
emacs-gtk3
emacs-gtk3-nativecomp
emacs-nox
emacs-x11
emacs-x11-nativecomp
1: <https://pkgs.alpinelinux.org/package/edge/community/x86/emacs>
2: <https://git.alpinelinux.org/aports/tree/community/emacs/APKBUILD>
a: https://issues.guix.gnu.org/issue/63050
b: https://yhetil.org/guix/87v8l1qy0j.fsf@gmail.com
Cheers,
simon
prev parent reply other threads:[~2023-08-23 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.87.1689091255.20905.help-guix@gnu.org>
2023-07-11 19:23 ` VSCode DevContainer for Guix? (Yasuaki Kudo) Zelphir Kaltstahl
2023-07-12 1:22 ` Yasuaki Kudo
2023-07-12 8:27 ` wolf
2023-07-12 11:27 ` Ekaitz Zarraga
2023-07-12 23:50 ` Yasuaki Kudo
2023-08-23 15:12 ` Simon Tournier [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
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=868ra13i8c.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=wolf@wolfsden.cz \
--cc=yasu@yasuaki.com \
--cc=zelphirkaltstahl@posteo.de \
/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).