From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Dariqq <dariqq@posteo.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
73028@debbugs.gnu.org,
"Florian Pelz" <pelzflorian@pelzflorian.de>
Subject: [bug#73028] [PATCH] doc: Document usage of #:out-of-source? for meson-build-system.
Date: Wed, 11 Sep 2024 15:09:10 +0900 [thread overview]
Message-ID: <878qvy3ent.fsf@gmail.com> (raw)
In-Reply-To: <f4bd571d1d0753acc003b4f1b371860e45270cce.1725467160.git.dariqq@posteo.net> (dariqq@posteo.net's message of "Wed, 4 Sep 2024 16:26:00 +0000")
Hi Dariqq,
Dariqq <dariqq@posteo.net> writes:
> Followup to 220546810830422f8ec3e6a4145fec85429914a1.
>
> * doc/guix.texi (meson-build-system): Document #:out-of-source? parameter.
>
> Change-Id: I730e1aef15010006a68710f8e46ce75dc50e6c67
> ---
> doc/guix.texi | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/doc/guix.texi b/doc/guix.texi
> index 16c697586a..2302e0f15c 100644
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> @@ -10146,6 +10146,10 @@ Build Systems
> of inputs, and they can be changed with the parameters @code{#:meson}
> and @code{#:ninja} if needed.
>
> +As Meson only supports out-of-source builds the @code{#:out-of-source?}
> +parameter specifies whether to search for license files in the source
> +or build directory.
> +
That strikes me as odd; is it useful in practice? Otherwise I'd rather
we keep it undocumented, so that it can be removed without notice in a
future cleanup (in a 'private API' way).
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-09-11 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 16:26 [bug#73028] [PATCH] doc: Document usage of #:out-of-source? for meson-build-system Dariqq
2024-09-11 6:09 ` Maxim Cournoyer [this message]
2024-09-11 15:18 ` Dariqq
2024-09-12 0:56 ` Maxim Cournoyer
2024-09-12 7:12 ` Dariqq
2024-09-12 12:02 ` Maxim Cournoyer
2024-09-12 19:19 ` Dariqq
2024-09-14 13:41 ` Maxim Cournoyer
2024-09-19 14:07 ` Dariqq
2024-09-22 5:57 ` Maxim Cournoyer
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=878qvy3ent.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=73028@debbugs.gnu.org \
--cc=dariqq@posteo.net \
--cc=ludo@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).