From: Maxime Devos <maximedevos@telenet.be>
To: Raghav Gururajan <rg@raghavgururajan.name>
Cc: 49238@debbugs.gnu.org, jgart@dismail.de
Subject: [bug#49238] [PATCH v1 2/2] gnu: Add ytfzf.
Date: Mon, 05 Jul 2021 14:13:32 +0200 [thread overview]
Message-ID: <a79af39fede525caaaa8ca336162620fc901750a.camel@telenet.be> (raw)
In-Reply-To: <c96b27b4-7fb4-1a40-046f-0721048e3c68@raghavgururajan.name>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
Raghav Gururajan schreef op ma 05-07-2021 om 08:03 [-0400]:
> [...]
> >
> > I'd suggest adding "patch" to 'native-inputs', adding the patch
> > to 'inputs' or 'native-inputs' (doesn't really matter which) and
> > doing (invoke "patch" OPTIONS "blabla.patch") before the substitute*.
> >
> > [...]
>
> I get the idea, but I don't think we can call .patch files inside
> phases, the patches directory is not exposed/available inside
> build-environment.
If the relevant patch files are added to 'inputs' or 'native-inputs',
then they are available in the build environment. As an example,
see the "libpng-apng" package. It adds the patch to 'inputs'
(named "apng") and invokes "patch" during the 'patch-apng' phase.
The "apng" input uses an 'origin' reference, but you could use
(local-file ...) there as well. Or beter: use 'search-patch'
instead.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-07-05 12:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 5:44 [bug#49238] Ytfzf Raghav Gururajan via Guix-patches via
2021-06-27 5:47 ` [bug#49238] [PATCH v1 1/2] gnu: Add python-ueberzug Raghav Gururajan via Guix-patches via
2021-06-27 5:47 ` [bug#49238] [PATCH v1 2/2] gnu: Add ytfzf Raghav Gururajan via Guix-patches via
2021-06-30 19:38 ` Maxime Devos
2021-07-05 12:03 ` Raghav Gururajan via Guix-patches via
2021-07-05 12:13 ` Maxime Devos [this message]
2021-07-05 12:20 ` Raghav Gururajan via Guix-patches via
2021-06-29 19:06 ` [bug#49238] [PATCH v2 1/2] gnu: Add python-ueberzug Raghav Gururajan via Guix-patches via
2021-06-29 19:06 ` [bug#49238] [PATCH v2 2/2] gnu: Add ytfzf Raghav Gururajan via Guix-patches via
2021-07-05 11:14 ` [bug#49238] [PATCH v3 1/2] gnu: Add python-ueberzug Raghav Gururajan via Guix-patches via
2021-07-05 11:14 ` [bug#49238] [PATCH v3 2/2] gnu: Add ytfzf Raghav Gururajan via Guix-patches via
2021-07-05 12:02 ` Maxime Devos
2021-07-05 12:19 ` Raghav Gururajan via Guix-patches via
2021-07-05 15:10 ` [bug#49238] [PATCH v5 1/2] gnu: Add python-ueberzug Raghav Gururajan via Guix-patches via
2021-07-05 15:10 ` [bug#49238] [PATCH v5 2/2] gnu: Add ytfzf Raghav Gururajan via Guix-patches via
2021-07-05 15:42 ` Maxime Devos
2021-07-06 5:25 ` Raghav Gururajan via Guix-patches via
2021-07-06 5:37 ` bug#49238: (no subject) Raghav Gururajan via Guix-patches via
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=a79af39fede525caaaa8ca336162620fc901750a.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=49238@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=rg@raghavgururajan.name \
/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.