From: Patrick Steinhardt <ps@pks.im>
To: Eli Schwartz <eschwartz@gentoo.org>
Cc: git@vger.kernel.org, Sam James <sam@gentoo.org>
Subject: Re: [PATCH v2] meson: disable coccinelle configuration when building from a tarball
Date: Wed, 26 Mar 2025 09:28:54 +0100 [thread overview]
Message-ID: <Z-O6xqjGmASjTZ9U@pks.im> (raw)
In-Reply-To: <20250325200920.198057-1-eschwartz@gentoo.org>
On Tue, Mar 25, 2025 at 04:08:48PM -0400, Eli Schwartz wrote:
> Wiring up coccinelle in the build, depends on running git commands to
> get the list of files to operate on. Reasonable, for a feature mainly
> used by people developing on git. If building git itself from a tarball
> distribution of git's own source code, one likely does not need to run
> coccinelle.
>
> But running those git commands failed, and caused the build to error
> out, if `spatch` was installed -- because the build assumed that its
> presence indicated a desire to use it on this source tree. Instead, we
> can expand the conditional to check for both `spatch` and the `.git`
> file or directory.
>
> Meson's `opt.require()` method allows us to add a prerequisite for the
> feature option. If the prerequisite fails, then the option either:
>
> - converts autodetection to disabled
>
> - emits an informative error if the feature was set to enabled:
> ```
> ERROR: Feature coccinelle cannot be enabled: coccinelle can only be run from a git checkout
> ```
Makes sense.
> Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
> ---
>
> v2: accidentally chopped off part of the commit message, sorry...
>
> contrib/coccinelle/meson.build | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/contrib/coccinelle/meson.build b/contrib/coccinelle/meson.build
> index 5d76a7fee6..ea054c924f 100644
> --- a/contrib/coccinelle/meson.build
> +++ b/contrib/coccinelle/meson.build
> @@ -1,4 +1,9 @@
> -spatch = find_program('spatch', required: get_option('coccinelle'))
> +coccinelle_opt = get_option('coccinelle').require(
> + fs.exists(meson.project_source_root() / '.git'),
> + error_message: 'coccinelle can only be run from a git checkout',
> +)
> +
> +spatch = find_program('spatch', required: coccinelle_opt)
> if not spatch.found()
> subdir_done()
> endif
>
> base-commit: c1d6628c9433c09ff62f916f2b933ee12995e9d8
Yup, makes sense, as well.
Thank you for the patch, looks good!
Patrick
prev parent reply other threads:[~2025-03-26 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 20:05 [PATCH] meson: disable coccinelle configuration when building from a tarball Eli Schwartz
2025-03-25 20:08 ` [PATCH v2] " Eli Schwartz
2025-03-25 23:21 ` Junio C Hamano
2025-03-25 23:29 ` Eli Schwartz
2025-03-26 8:28 ` Patrick Steinhardt [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z-O6xqjGmASjTZ9U@pks.im \
--to=ps@pks.im \
--cc=eschwartz@gentoo.org \
--cc=git@vger.kernel.org \
--cc=sam@gentoo.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.
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 NNTP newsgroup(s).