all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: 58760@debbugs.gnu.org
Cc: control@debbugs.gnu.org
Subject: bug#58760: Guix System iso too big for cdrom again
Date: Wed, 02 Nov 2022 16:27:04 +0100	[thread overview]
Message-ID: <8735b1xtpz.fsf@pelzflorian.de> (raw)
In-Reply-To: <87tu3tjjbc.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Mon, 24 Oct 2022 18:08:23 +0200")

close 58760
thanks

Thank you all for your responses.  But I have closed the issue (without
really trying the methods) because

Tobias writes:
> But we can go deeper if we choose to, by dropping zisofs and going for
> something like squashfs, which achieves higher compression through
> higher block sizes and better algorithms like XZ.

Probably yes, though I don’t dare writing that and

Csepp writes:
> Are there unnecessary dependencies that could be cut out?

Kind of, but only by making variant packages without the dependencies
that Maxime listed in his response, just for the installer, but it would
not be enough to get below 700MB.

Maxime writes:
> I think -Os would be worth investigating.

Yes, that would be easiest, though looking at --tune, I guess making
variant base packages with -Os just for the installer is not worth the
complexity since cdroms are a niche use-case.

It would be possible, so maybe I shouldn’t have closed, but maybe I
shouldn’t have filed the issue in the first place.

Regards,
Florian




      parent reply	other threads:[~2022-11-02 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 16:08 bug#58760: Guix System iso too big for cdrom again pelzflorian (Florian Pelz)
2022-10-24 17:51 ` Csepp
2022-10-24 18:14 ` Maxime Devos
2022-10-24 18:17 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-11-02 15:27 ` pelzflorian (Florian Pelz) [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=8735b1xtpz.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=58760@debbugs.gnu.org \
    --cc=control@debbugs.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.