public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andreas Sturmlechner <asturm@gentoo.org>
To: gentoo-dev@lists.gentoo.org, kde@gentoo.org, base-system@gentoo.org
Subject: Re: [gentoo-dev] [PATCH] cmake.eclass: Add recursive CMakeLists.txt unsupported version detection
Date: Sat, 17 May 2025 23:30:34 +0200	[thread overview]
Message-ID: <2319831.iZASKD2KPV@tuxbrain.fritz.box> (raw)
In-Reply-To: <aCj5rtfNQZvQhwVt@eversor>

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

On Samstag, 17. Mai 2025 22:42:30 Mitteleuropäische Sommerzeit Ionen Wolkens 
wrote:
> Just to note, may be rare so guess not a big deal but, while crawling
> all sub-directories, it could pickup some extra CMakeLists.txt that are
> entirely unused (by us) and don't need attention downstream.

On Samstag, 17. Mai 2025 23:03:42 Mitteleuropäische Sommerzeit Ionen Wolkens 
wrote:
> Haven't looked at that closely code-wise though, it'd be nicer to
> avoid doing grep twice.

Could address both points by limiting the crawling to maxdepth 1 or 2 and 
always do the regex, without pre-filtering through a first grep, and probably 
catch most of the brokenness.

However, that would have already failed media-libs/opencv-4.10 which in its 
most extreme case had too low a minimum version even 6 subdirs deep... otoh I 
already know of at least digikam also causing false warnings in its subdirs - 
but then these are only one or two upstream build system changes away from 
becoming errors.

Regards

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 789 bytes --]

  reply	other threads:[~2025-05-17 21:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-17 20:04 [gentoo-dev] [PATCH] cmake.eclass: Add recursive CMakeLists.txt unsupported version detection Andreas Sturmlechner
2025-05-17 20:42 ` Ionen Wolkens
2025-05-17 21:03   ` Ionen Wolkens
2025-05-17 21:30     ` Andreas Sturmlechner [this message]
2025-05-18  2:42   ` Eli Schwartz
2025-05-19 18:44 ` [gentoo-dev] [PATCH v2 1/3] " Andreas Sturmlechner
2025-05-19 18:46   ` [gentoo-dev] [PATCH v2 2/3] cmake.eclass: If CMake 4 is detected, build w/ compat cmake arg Andreas Sturmlechner
2025-05-19 18:47   ` [gentoo-dev] [PATCH v2 3/3] cmake.eclass: Add CMAKE_QA_COMPAT_SKIP flag to skip compat checks Andreas Sturmlechner
2025-05-19 18:51   ` [gentoo-dev] [PATCH v2 1/3] cmake.eclass: Add recursive CMakeLists.txt unsupported version detection Michał Górny
2025-05-19 18:58     ` Andreas Sturmlechner
2025-06-02 20:44 ` [gentoo-dev] [PATCH v3 " Andreas Sturmlechner
2025-06-02 20:46   ` [gentoo-dev] [PATCH v3 2/3] cmake.eclass: If CMake 4 is detected, build w/ compat cmake arg Andreas Sturmlechner
2025-06-02 20:47   ` [gentoo-dev] [PATCH v3 3/3] cmake.eclass: Add CMAKE_QA_COMPAT_SKIP flag to skip compat checks Andreas Sturmlechner

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=2319831.iZASKD2KPV@tuxbrain.fritz.box \
    --to=asturm@gentoo.org \
    --cc=base-system@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=kde@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