From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 42123@debbugs.gnu.org
Subject: [bug#42123] [PATCH] linux-libre: Enable module compression.
Date: Tue, 07 Jul 2020 09:32:43 +0200 [thread overview]
Message-ID: <874kqjn5k4.fsf@gnu.org> (raw)
In-Reply-To: <871rloiept.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 06 Jul 2020 22:13:50 +0200")
Hey Ludo!
> As for the location… I think the reason things are like this is to avoid
> having everything depend on (guix self), but maybe that’s OK after all?
>
> If the zlib bindings were an external package, things would be easier
> because we wouldn’t have to do this (guix config) dance.
>
> More generally, we should look at all the uses of (guix config) and see
> whether/how we can get rid of them.
>
> But I digress… Thoughts?
Thanks for your quick feedback. Given the time I spent debugging this
issue, I agree that this (guix config) module thing is hard to deal
with.
If it works for you, I could create three new Guile libraries:
* Guile-libz
* Guile-liblz
* Guile-xz
or maybe just,
* Guile-compression
It would help us getting rid of (guix config) as you proposed.
WDYT?
Thanks,
Mathieu
next prev parent reply other threads:[~2020-07-07 7:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 14:24 [bug#42123] [PATCH] linux-libre: Enable module compression Mathieu Othacehe
2020-06-30 7:31 ` Mathieu Othacehe
2020-07-02 10:23 ` Ludovic Courtès
2020-07-06 8:48 ` Mathieu Othacehe
2020-07-06 12:20 ` Ludovic Courtès
2020-07-06 14:23 ` Mathieu Othacehe
2020-07-06 20:13 ` Ludovic Courtès
2020-07-07 7:32 ` Mathieu Othacehe [this message]
2020-07-09 7:56 ` Ludovic Courtès
2020-07-27 16:24 ` Mathieu Othacehe
2020-07-28 22:16 ` Ludovic Courtès
2020-08-06 13:44 ` Mathieu Othacehe
2020-08-23 16:27 ` Ludovic Courtès
2020-08-24 11:38 ` Mathieu Othacehe
2020-08-24 14:03 ` Ludovic Courtès
2020-08-25 10:30 ` bug#42123: " Mathieu Othacehe
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=874kqjn5k4.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=42123@debbugs.gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).