[CMake] Update two CMake policies to NEW.#22145
Open
hageboeck wants to merge 1 commit intoroot-project:masterfrom
Open
[CMake] Update two CMake policies to NEW.#22145hageboeck wants to merge 1 commit intoroot-project:masterfrom
hageboeck wants to merge 1 commit intoroot-project:masterfrom
Conversation
The two policies in question should not affect ROOT: - ROOT does not use <PACKAGENAME>_ROOT for purposes other than finding a package, so the NEW version of the policy is fine. - And it is preferable to update the timestamps of files extracted from an archive if the URL changes (NEW) as opposed to keeping the timestamps found in the archive (OLD).
Test Results 22 files 22 suites 3d 13h 45m 42s ⏱️ Results for commit d228a1c. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The two policies in question should not affect ROOT:
<PACKAGENAME>_ROOTfor purposes other than finding a package, so the NEW version of the policy is fine.