From: Lars-Dominik Braun <lars@6xq.net>
To: Attila Lendvai <attila@lendvai.name>
Cc: "Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>,
"Ian Eure" <ian@retrospec.tv>, guix-devel <guix-devel@gnu.org>
Subject: Re: Request for assistance maintaining LibreWolf
Date: Sun, 18 Aug 2024 11:07:06 +0200 [thread overview]
Message-ID: <ZsG5ujdqPMmsOfUW@noor.fritz.box> (raw)
In-Reply-To: <GM9ZYT1WtT4ecO6LmecjhDXtpFgzz9AjfOlPPYcLtEhqL_7uWw-j099ishR8jCT9PPTcswuduZognk3XvRQnBzEsk7StZGFRRJJZ1WANUqQ=@lendvai.name>
Hi,
> so, i think a lot of packages should be in channels. probably everything that is not essential for a minimally functional system that can bootstrap itself. part of python could be in the main guix repo, but whatever is not tightly needed could go into a channel with its own access control management.
I have the same feeling. As I wrote on IRC a while ago[1]: “Perhaps
the Docker faction is right and traditional distributions are dead,
because they simply cannot (with reasonable effort) provide a coherent
set of packages any more. Maybe we have to embrace that approach and
reduce Guix to a minimal set of packages needed to build Guix itself
and then build (possibly incompatible) channels on top of that.”
For alot of the more complex packages we’ll probably have to go as far
as having a separate channel for each of them. And thus a prerequisite
for this setup to work is that this hypothetical “Guix Zero” will
have excellent support for dozens of channels with even more modules
inside of them[2].
Lars
[1] https://logs.guix.gnu.org/guix-hpc/2024-05-03.log#102354
[2] I believe Guile is still the limiting factor here, since there’s
a maximum number of modules that can be loaded.
next prev parent reply other threads:[~2024-08-18 9:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 16:44 Request for assistance maintaining LibreWolf Ian Eure
2024-08-17 18:00 ` Sergio Pastor Pérez
2024-08-17 19:43 ` Ian Eure
2024-08-18 8:35 ` Christopher Baines
2024-08-18 16:50 ` Ian Eure
2024-08-19 1:53 ` Suhail Singh
2024-08-19 8:53 ` Christopher Baines
2024-08-19 23:14 ` Ian Eure
2024-09-12 1:01 ` Maxim Cournoyer
2024-08-19 17:01 ` Sergio Pastor Pérez
2024-08-18 8:37 ` Attila Lendvai
2024-08-18 9:07 ` Lars-Dominik Braun [this message]
2024-08-17 20:36 ` Ian Eure
2024-08-17 23:08 ` Suhail Singh
2024-08-18 4:07 ` Ian Eure
2024-08-18 21:17 ` Tomas Volf
2024-08-21 20:54 ` Ludovic Courtès
2024-08-22 15:00 ` Ian Eure
2024-08-28 20:48 ` Ludovic Courtès
2024-08-28 23:15 ` Ian Eure
2024-08-29 7:30 ` Tobias Geerinckx-Rice
2024-08-29 20:24 ` [Browser-Team] " André Batista
2024-08-30 20:14 ` Ludovic Courtès
2024-08-22 16:37 ` André Batista
2024-08-28 20:46 ` Ludovic Courtès
2024-08-30 20:18 ` Defining the role of teams Ludovic Courtès
2024-08-28 23:16 ` Request for assistance maintaining LibreWolf Ian Eure
[not found] <mailman.5970.1723926982.21382.guix-devel@gnu.org>
2024-08-18 0:11 ` Andy Tai
2024-08-18 0:48 ` Ian Eure
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=ZsG5ujdqPMmsOfUW@noor.fritz.box \
--to=lars@6xq.net \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=ian@retrospec.tv \
--cc=sergio.pastorperez@outlook.es \
/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.