unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jbranso@dismail.de
To: "Andy Tai" <atai@atai.org>, guix-devel@gnu.org
Subject: Re: setting up a channel for pending package update patches
Date: Sat, 02 Mar 2024 23:08:38 +0000	[thread overview]
Message-ID: <e0ff2924be5e1c0a4412f4d75f8d09530d5d3091@dismail.de> (raw)
In-Reply-To: <CAJsg1E-MNdJ58PzK20V5m5uQWg59azSE-gmxCkFCgyU_mU62Tg@mail.gmail.com>

March 2, 2024 at 4:53 PM, "Andy Tai" <atai@atai.org> wrote:



> 
> Hi, curious if anyone has done such a task: setting up a channel for
> the pending patches for package definitions.

I believe you are describing the guixrus channel.

https://sr.ht/~whereiseveryone/guixrus/

They will take WIP packages, and they help you to merge them upstream.

Joshua

> 
> Since pending patches for package updates take long time to process
> and merge. I wonder if anyone has set up a channel that contains the
> patches applied on top of the Guix git repo so such a channel would
> bring the pending changes to end users who use this channel before the
> official Guix git repo is updated (applying the package definition
> patches).
> 
> This is not about a permanent fork of the Guix repo or a special
> channel like guix games for some specific types of packages like say
> games.
> 
> Better yet, if anyone has set up a substitution server for this update
> channel, info on that would be even better.
> 
> This is assuming some risks, such as update patches may have errors,
> that may break things
> 
> Curious if anyone's experience in doing this, any issues running such
> setup, etc.
>


      reply	other threads:[~2024-03-02 23:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02 21:53 setting up a channel for pending package update patches Andy Tai
2024-03-02 23:08 ` jbranso [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=e0ff2924be5e1c0a4412f4d75f8d09530d5d3091@dismail.de \
    --to=jbranso@dismail.de \
    --cc=atai@atai.org \
    --cc=guix-devel@gnu.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).