Hi,
Just giving my 2 cents:
If the preferred solution is the "POLICY_NEW_UNTIL" wording, then why not make
this accepted as well? This way, you can deprecate the backwards-compatible
version in a few years and remove it some time thereafter. In the end, you'll
get a cleaner solution...
Cheers,
On Mon, Jul 2, 2018 at 4:04 AM, Alan W. Irwin
wrote:
> On 2018-07-01 08:12+1000 Craig Scott wrote:
>
> Older CMake versions
>> will see the extra dots as being version component separators and will end
>> up effectively ignoring the max part.
>>
>
> This explanation of how "..." will be interpret
Thanks for the link.
The backwards compatibility is something worth mentioning in the release notes,
so that people can use it right away.
Am 1. Juli 2018 00:12:19 MESZ schrieb Craig Scott :
>(Subject changed to be specific to this discussion)
>
>On Sat, Jun 30, 2018 at 3:13 PM, Hendrik Sattler
(Subject changed to be specific to this discussion)
On Sat, Jun 30, 2018 at 3:13 PM, Hendrik Sattler
wrote:
> It would actually make even more sense to rename cmake_minimum_required()
> to cmake_version_required() with the new syntax or something similar. Users
> of the old function cannot use t
