From: Josselin Poiret <dev@jpoiret.xyz>
To: jgart <jgart@dismail.de>, guix-devel@gnu.org
Subject: Re: Stratification of GNU Guix into Independent Channels
Date: Sat, 24 Dec 2022 12:37:17 +0100 [thread overview]
Message-ID: <87pmc9jamq.fsf@jpoiret.xyz> (raw)
In-Reply-To: <84400bcea3eee39dc15d82812a8006bb@dismail.de>
Hi jgart,
IMO, having everything in one repo, while going against the "modularity"
philosophy, really helps a lot when updating packages. In my experience
with the Other Channel That We Should Not Talk About, there often are
breaking changes in the main repository that lead to the other channel
being broken for a couple of days. It would take way longer for changes
to propagate things to the "leaf" channels.
Also, you can't reasonably expect programs to be categorized that well
(although I'm pretty sure there could be consensus on non-PITA
vs. PITA-packages with the usual suspects :) ).
I don't think there is a way to reconcile the "complete system
distribution" and "completely modular distribution" viewpoints, at least
at that level. The channels approach that exists for now is a nice
pragmatic solution that still allows quite a lot of freedom.
Best,
--
Josselin Poiret
next prev parent reply other threads:[~2022-12-24 11:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 3:49 Stratification of GNU Guix into Independent Channels jgart
2022-12-24 4:31 ` Vagrant Cascadian
2022-12-24 12:31 ` Joshua Branson
2022-12-24 5:24 ` jgart
2022-12-24 8:37 ` Stratification of GNU Guix into Independent Channels, X-mas and Guix days! Pjotr Prins
2022-12-25 12:00 ` indieterminacy
2022-12-25 16:27 ` jgart
2022-12-24 11:01 ` Stratification of GNU Guix into Independent Channels Liliana Marie Prikler
2022-12-24 11:37 ` Josselin Poiret [this message]
2022-12-27 13:50 ` Hartmut Goebel
2022-12-29 1:25 ` Denis 'GNUtoo' Carikli
2023-01-03 13:26 ` zimoun
2023-01-27 7:47 ` Giovanni Biscuolo
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=87pmc9jamq.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.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.
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).