Hi Zacchaeus,
This could be our way out, but it also means that Guix needs to
make
it even easier to deal with extra channels. So far adding a
new
channel has always felt a little heavy. A few commands to
manage
channels might lower the threshold. Recently we've got command
line
options to fetch a channels file to pull from; working a little
more
in that direction might make channels cheap enough to make it
more
attractive to keep packages independent of the collection
that's part
of Guix.
You are thinking about it too much. The point is, development
of core
Guix should not be hindered by LLM assisted PRs and/or
vibe-coded
packages that encumber without adding enough value. Make the
d*** LLM
channel, and let them deal with making it work well.
This would be a choice, and making choices with a little bit of
foresight is why we are discussing this.
As a project we should certainly not host a channel for things
that we don't take responsibility for. Whoever wants to have a
vibecode channel doesn't need the project to make it for them, but
it would benefit the project as a whole if we ironed out the kinks
in dealing with more than a handful of channels.
The discussion is about where we draw the line with regard to what
we spend our volunteer time on. Reviews and even the most basic
of quality control takes time; disposable software doesn't deserve
to drain that limited pool of time.
--
Ricardo
