From: Suhail Singh <suhailsingh247@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Simon Josefsson via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org>,
Cayetano Santos <csantosb@inventati.org>,
Simon Josefsson <simon@josefsson.org>
Subject: Splitting up Guix channel (was: On the quest for a new release model)
Date: Sat, 14 Dec 2024 12:21:02 -0500 [thread overview]
Message-ID: <87h676kwox.fsf_-_@gmail.com> (raw)
In-Reply-To: <87zfkyr6gw.fsf@elephly.net> (Ricardo Wurmus's message of "Sat, 14 Dec 2024 09:53:19 +0100")
Ricardo Wurmus <rekado@elephly.net> writes:
> This has been discussed in the past and it is far from trivial.
> Consider that glibc needs Python at build time and the Linux kernel may
> need Rust. Consider also that it is easy to introduce a package from
> the outer ring to the inner ring through transitive dependencies.
You are pointing out issues which would be necessary to overcome. Based
on what you've said, it's not clear to me that overcoming these would
not be feasible.
> Yes, there are many leaf packages, but it seems to me that it's a fool's
> errand to attempt to separate packages like this.
Is the fact that distributions like OpenSUSE Tumbleweed accomplish such
a separation not material? I agree that no definitive conclusion can be
drawn from their success since the set of packages aren't the same. And
yet, I am not aware of anything that precludes such a separation.
> It's certainly not work that should be done manually.
Agreed.
--
Suhail
prev parent reply other threads:[~2024-12-14 17:21 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 12:19 Discussion notes on releases and branches Andreas Enge
2023-02-12 21:13 ` Moving forward with teams and feature branches (was: Discussion notes on releases and branches) Josselin Poiret
2023-02-12 21:34 ` Andreas Enge
2023-02-13 9:32 ` Time for RFC? (was Re: Moving forward with teams and feature branches (was: Discussion notes on releases and branches)) zimoun
2023-02-13 14:07 ` Moving forward with teams and feature branches (was: Discussion notes on releases and branches) Andreas Enge
2023-02-14 19:12 ` Leo Famulari
2023-02-13 9:22 ` Release (was " Simon Tournier
2023-02-14 10:14 ` Rust team branch " Efraim Flashner
2023-02-14 16:36 ` Rust team branch Andreas Enge
2023-02-14 20:07 ` Efraim Flashner
2023-02-16 10:56 ` Andreas Enge
2023-02-14 16:36 ` Rust team branch (was Re: Discussion notes on releases and branches) Katherine Cox-Buday
2023-02-14 20:08 ` Efraim Flashner
2023-02-15 17:49 ` Katherine Cox-Buday
2023-03-17 15:24 ` Discussion notes on releases and branches Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-18 17:42 ` Leo Famulari
2024-12-13 8:37 ` On the quest for a new release model (was: Discussion notes on releases and branches) Cayetano Santos
2024-12-13 12:03 ` On the quest for a new release model Ricardo Wurmus
2024-12-13 13:01 ` Suhail Singh
2024-12-13 15:21 ` Greg Hogan
2024-12-13 15:52 ` Suhail Singh
2024-12-13 16:05 ` Suhail Singh
2024-12-13 16:28 ` Cayetano Santos
2024-12-13 17:21 ` Suhail Singh
2024-12-13 20:34 ` Cayetano Santos
2024-12-13 22:13 ` Ricardo Wurmus
2024-12-13 22:27 ` Suhail Singh
2024-12-13 23:08 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-12-14 1:38 ` John Kehayias via Development of GNU Guix and the GNU System distribution.
2024-12-14 17:18 ` kiasoc5
2024-12-14 18:00 ` Cayetano Santos
2024-12-13 16:04 ` Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2024-12-13 17:47 ` Suhail Singh
2024-12-13 20:14 ` Tomas Volf
2024-12-13 22:13 ` Suhail Singh
2024-12-14 8:59 ` Ricardo Wurmus
2024-12-14 14:23 ` Suhail Singh
2024-12-14 12:26 ` Tomas Volf
2024-12-14 14:49 ` Suhail Singh
2024-12-14 8:53 ` Ricardo Wurmus
2024-12-14 17:21 ` Suhail Singh [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=87h676kwox.fsf_-_@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=csantosb@inventati.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=simon@josefsson.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).