all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Suhail Singh <suhailsingh247@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "Greg Hogan" <code@greghogan.com>,
	"Noé Lopez" <noe@xn--no-cja.eu>,
	guix-devel@gnu.org
Subject: Re: Forge and build automation
Date: Sat, 26 Oct 2024 12:51:04 -0400	[thread overview]
Message-ID: <87ldya6c5j.fsf@gmail.com> (raw)
In-Reply-To: <87cyjmylej.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Sat, 26 Oct 2024 16:43:48 +0200")

Ludovic Courtès <ludo@gnu.org> writes:

>> WIth 29,000+ packages the nature of the project has changed from
>> adding new software to managing updates (what fraction of new packages
>> are rust or python dependencies?).
>
> … that’s the crux of the problem.  What works for our little channels
> mentioned above is insufficient for the main ‘guix’ channel.

Why does the main 'guix' channel have to contain the "entire world"?

> Besides, I agree with you Greg that we need more automation, in
> particular for package updates.  Nixpkgs has an auto-update bot; we
> could just as well have a bot that roughly runs ‘guix refresh’ and
> submits patches/merge requests.  I’m sure somebody will end up
> scratching this particular itch, it’s such an obvious thing to do.

Where would such a bot run?  Do we have an example of a bot that runs in
a similar context?

-- 
Suhail


  reply	other threads:[~2024-10-26 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 14:21 Discussion on Guix funding // future Noé Lopez via Development of GNU Guix and the GNU System distribution.
2024-10-25 21:26 ` Greg Hogan
2024-10-26 14:43   ` Forge and build automation Ludovic Courtès
2024-10-26 16:51     ` Suhail Singh [this message]
2024-10-26 22:12       ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2024-10-28 13:10 Simon Tournier

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=87ldya6c5j.fsf@gmail.com \
    --to=suhailsingh247@gmail.com \
    --cc=code@greghogan.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=noe@xn--no-cja.eu \
    /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.