> How is quality control supposed to work? Already now we have friction
> between Guix proper and channels (this actually prompted GCD 006,
> because guix-science complained about removal of packages in Guix proper).
> For instance, assuming that a certain set of Python packages is moved
> into a channel of its own and we want to update to python-3.13 in Guix
> proper, how would we do that? Right now the Python team takes respons-
> ibility for breakage in dependent packages (and they are not necessarily
> happy about it). In the future, do we agree that Guix proper does the
> update, and channels are responsible for following (or breaking)? And
> then people might not even be able to do a "guix pull" anymore if their
> channels file contains a broken channel?


here's a raw idea:

add new channel feature: compatibility ranges (typically it would be
just an optional list of
'compatible-until-this-commit-of-that-channel', but it's worth
pondering about a generalization of this).

if something breaks then record the new finding as a constraint using
the above mechanism.

i think both directions should be representable, so that e.g. the guix
channel could also mark a random-abandoned-channel as incompatible
beyond a certain commit. whoever is more agile could step up first to
create an entry of incompatibility.

guix pull would pull the git repos, but update the worktrees only up
until the latest commit that is still compatible, and then point out
if/why everything is held back.

add an --ignore-and-try-anyway for good measure.

user can decide to (1) live with the outdated packages, (2) fix the
issue, or (3) stop pulling from the channel holding everything back.

this information should be represented in a way that normal git
commits can alter; i.e. changing it would be part of the normal dev
process.

--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
There's one thing in common in all your past failed relationships: you.


Reply via email to