From: Peter Mikkelsen <petermikkelsen10@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28444@debbugs.gnu.org
Subject: [bug#28444] [PATCH 2/3] gnu: Add meson-for-build.
Date: Fri, 15 Sep 2017 23:00:52 +0200 [thread overview]
Message-ID: <CADh9keXUaC+yWY_i4geAgfgyOfwmnTwvHOk_H5_AHFoPoXiuhw@mail.gmail.com> (raw)
In-Reply-To: <87fubnllxm.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
Den 15. sep. 2017 22.57 skrev "Ludovic Courtès" <ludo@gnu.org>:
Peter Mikkelsen <petermikkelsen10@gmail.com> skribis:
> * gnu/packages/build-tools.scm (meson-for-build): New variable.
> * gnu/packages/patches/meson-for-build-rpath.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Register it.
Applied!
I’ve marked it as “hidden” so that it doesn’t show up in UIs (patch
below). Let me know if you think that’s not OK!
I didn't know that was possible, but it seems like the right thing to do,
thanks :)
[-- Attachment #2: Type: text/html, Size: 1075 bytes --]
next prev parent reply other threads:[~2017-09-15 21:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 12:48 [bug#28444] [PATCH 0/3] Add meson-build-system Peter Mikkelsen
2017-09-13 12:50 ` [bug#28444] [PATCH 1/3] gnu: meson: Update to 0.42.0 Peter Mikkelsen
2017-09-13 12:50 ` [bug#28444] [PATCH 2/3] gnu: Add meson-for-build Peter Mikkelsen
2017-09-15 20:57 ` Ludovic Courtès
2017-09-15 21:00 ` Peter Mikkelsen [this message]
2017-09-13 12:50 ` [bug#28444] [PATCH 3/3] build-system: Add 'meson-build-system' Peter Mikkelsen
2017-09-15 21:07 ` Ludovic Courtès
2017-09-16 11:08 ` Peter Mikkelsen
2017-09-16 16:11 ` bug#28444: " Ludovic Courtès
2017-09-16 17:06 ` [bug#28444] " Peter Mikkelsen
2017-09-17 13:19 ` Ludovic Courtès
2017-09-17 13:24 ` Peter Mikkelsen
2017-09-17 14:01 ` Peter Mikkelsen
2017-09-17 19:21 ` Ludovic Courtès
2017-09-15 20:53 ` [bug#28444] [PATCH 1/3] gnu: meson: Update to 0.42.0 Ludovic Courtès
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=CADh9keXUaC+yWY_i4geAgfgyOfwmnTwvHOk_H5_AHFoPoXiuhw@mail.gmail.com \
--to=petermikkelsen10@gmail.com \
--cc=28444@debbugs.gnu.org \
--cc=ludo@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).