From: Tomas Volf <~@wolfsden.cz>
To: Suhail Singh <suhailsingh247@gmail.com>
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: Re: On the quest for a new release model
Date: Sat, 14 Dec 2024 13:26:35 +0100 [thread overview]
Message-ID: <87ed2alabo.fsf@wolfsden.cz> (raw)
In-Reply-To: <87msgzb599.fsf@gmail.com> (Suhail Singh's message of "Fri, 13 Dec 2024 17:13:54 -0500")
[-- Attachment #1: Type: text/plain, Size: 2324 bytes --]
Suhail Singh <suhailsingh247@gmail.com> writes:
> Tomas Volf <~@wolfsden.cz> writes:
>
>> I would like to point out that there is more work involved than just
>> splitting it into separate channels and adding those into
>> %default-channels.
>
> Could you please elaborate? Or were these the two points you noted
> below?
Yes, I have meant that the various issues would need to be fixed or
figured out.
>
>> While multiple channels do work well with guix pull, there are annoying
>> limitations when used in other places.
>
> Could you please share some references for this?
Definitely. I personally have run into these two issues:
#74396
When you install system-wide guix with multiple channels, it shadows
channels from your guix-pulled guix (except for 'guix channel). That
was unpleasant surprise.
guix-for-channels does not cache
`guix-for-channels' procedure is a way how to produce a guix package
for a channel list. However it does not cache the computation, so it
is extremely slow when actually used. I wrote a bit about that here:
https://wolfsden.cz/blog/post/what-goes-into-guix-shaped-hole.html .
I am not sure if there are more, but my impression is that using
multiple channels (outside of guix-pull) is not well explored territory,
so I would not be surprised.
>
>> Also you would need some way to specify what channel commits are able to
>> work together version-wise.
>
> Let's say we have two channels in the future: $guix-slim and
> $guix-extras. Wouldn't it be sufficient for $guix-extras to depend on
> $guix-slim ? If not, could you please elaborate?
You say depend on guix-slim, but on *what* commit from guix-slim? You
can pin channels. What happens when you pin guix-slim, but pull
guix-extras? I believe some human readable error should be given, not a
failure to build something due to, for example, not having the required
version of gcc now (for example because guix-extras increased the
required version).
Also what about substitutes? Which combinations of commits will have
substitutes built?
I just feel there is a lot to figure out with this proposal.
Have a nice day,
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
next prev parent reply other threads:[~2024-12-14 12:27 UTC|newest]
Thread overview: 40+ 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:04 ` bug#61475: Staging branch (was: Moving forward with teams and feature branches) Andreas Enge
2023-05-10 2:55 ` Maxim Cournoyer
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-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 [this message]
2024-12-14 14:49 ` Suhail Singh
2024-12-14 8:53 ` Ricardo Wurmus
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=87ed2alabo.fsf@wolfsden.cz \
--to=~@wolfsden.cz \
--cc=csantosb@inventati.org \
--cc=guix-devel@gnu.org \
--cc=simon@josefsson.org \
--cc=suhailsingh247@gmail.com \
/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.