unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Graves <ngraves@ngraves.fr>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>,
	Guix Devel <guix-devel@gnu.org>
Subject: Re: Search path for patches
Date: Sat, 14 Sep 2024 00:05:03 +0200	[thread overview]
Message-ID: <87seu3nrao.fsf@ngraves.fr> (raw)
In-Reply-To: <m11q1nqx0g.fsf@fastmail.net>

On 2024-09-13 19:33, Konrad Hinsen wrote:

> Hi everyone,
>
> I have been searching for a while, without much success, so I am trying
> to tap into your collective wisdom: What's the search path used by
> search-patches?
>
> More precisely, where do I have to put patches
>  1. In a channel?
>  2. In a directory added to GUIX_PACKAGE_PATH/GUILE_LOAD_PATH?
>
> The main Guix channel has a "patches" directory inside "packages".  The
> channel guix-science has it at the root. For my own channel that I am
> trying to set up, neither seems to work so far.

Not a direct answer, but I use the approach I've found in guixrus:

      (patches
        (parameterize
            ((%patch-path
              (map
               (lambda (directory)
                 (string-append directory "/guixrus/packages/patches"))
               %load-path)))
        (search-patches
         ;;patches created from github issues
         "lxappearence-gtk3-01-only-do-x11-on-x11.patch"
         "lxappearence-gtk3-02-set-some-settings-gsettings.patch")))

This is allows you to put patches quite conveniently in a channel.

-- 
Best regards,
Nicolas Graves


  parent reply	other threads:[~2024-09-13 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 17:33 Search path for patches Konrad Hinsen
2024-09-13 18:30 ` Ekaitz Zarraga
2024-09-13 22:05 ` Nicolas Graves [this message]
2024-09-15  8:14   ` Konrad Hinsen
2024-09-15  8:04 ` Liliana Marie Prikler
2024-09-16 16:23   ` Konrad Hinsen

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=87seu3nrao.fsf@ngraves.fr \
    --to=ngraves@ngraves.fr \
    --cc=guix-devel@gnu.org \
    --cc=konrad.hinsen@fastmail.net \
    /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).