Fair enough but could we at least have a way to turn it off if we know what it's about but still want to keep our dependencies lower than what ever current frameworks happens to decide on.
May 16, 2022 2:02:26 PM Christoph Cullmann (cullmann.io) <christ...@cullmann.io>: > On 2022-05-16 19:38, Alexander Neundorf wrote: >> On Dienstag, 3. Mai 2022 18:43:48 CEST Méven wrote: >>> Le mar. 3 mai 2022 à 18:25, Thomas Friedrichsmeier < >>> thomas.friedrichsme...@kdemail.net> a écrit : >>>> On Tue, 3 May 2022 10:35:20 +0200 >>>> >>>> Méven <meve...@gmail.com> wrote: >>>>> I am guessing you are using cmake >= 3.16 so it allows you to run, but >>>>> since the project does not have a cmake minimum, for others using >>>>> cmake < 3.16 the build will break. >>>>> This warning highlights it, so you inform your contributor they need >>>>> cmake 3.16 before running into the hard fail in FindKF5. >>>> >>>> On the downside, project wishing to remain backwards-compatible with >>>> older systems (which will come with older versions of both cmake and >>>> ECM) will want to avoid adding such a requirement, explicitly. >>> Cmake 3.16 dates from November 2019 to put things in perspective. >> RHEL 8, which many commercial users have not updated to yet, comes with cmake >> 3.11, to add some more perspective ;-) > > Yeah, that is true, but to be realistic: We do commercial software development > and even need to stick with RHEL 7 and we do what everybody else does: > > Just install a proper cmake during both the CI and the normal development. > > We even install our own compilers or at least the latest devtoolset, > otherwise RHEL 7 is useless. > > I don't think the enterprise distros are anything we should really look at > for determining our dependency versions. > > Greetings > Christoph > >> Alex > > -- > Ignorance is bliss... > https://cullmann.io | https://kate-editor.org
signature.asc
Description: PGP signature
