-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore printing full paths to files containing absolute paths. #1455
Restore printing full paths to files containing absolute paths. #1455
Conversation
@autoantwort points out that it makes sense for those to be clickable. He also wants us to drop the note: prefix from newlines if we aren't attached to a tty; I'm not sure if that is correct.
@@ -1283,7 +1283,7 @@ DECLARE_MESSAGE(FilesContainAbsolutePath1, | |||
"followed by a list of found files.", | |||
"There should be no absolute paths, such as the following, in an installed package. To suppress this " | |||
"message, add set(VCPKG_POLICY_SKIP_ABSOLUTE_PATHS_CHECK enabled)") | |||
DECLARE_MESSAGE(FilesContainAbsolutePath2, (), "", "Absolute paths were found in the following files") | |||
DECLARE_MESSAGE(FilesContainAbsolutePath2, (), "", "Absolute paths found here") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DECLARE_MESSAGE(FilesContainAbsolutePath2, (), "", "Absolute paths found here") | |
DECLARE_MESSAGE(FilesContainAbsolutePath2, (), "", "absolute paths found here") |
@@ -966,11 +964,9 @@ foreach ($bad_dir in @('build-dir', 'downloads', 'installed-root', 'package-dir' | |||
|
|||
$expectedFooter = @" | |||
$($PortfilePath): note: Adding a call to ``vcpkg_fixup_pkgconfig()`` may fix absolute paths in .pc files | |||
note: Absolute paths were found in the following files | |||
$($packagesRoot)$($NativeSlash)vcpkg-policy-absolute-paths_$($Triplet): note: the files are relative to `${CURRENT_PACKAGES_DIR} here | |||
note: include/vcpkg-policy-absolute-paths.h |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am a bit sad to lose the form that a user would say in portfile.cmake
in order to edit one of these files but making the paths clickable is probably worth it anyway... should we keep printing ${CURRENT_PACKAGES_DIR}
here to make it easier for the user to figure that out?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can see arguments either way... though doesn't this apply to most post-lint checks? Maybe it should be centralized (printed once at the beginning or end of the post-lint checks if any fired)
Old style
Current
New
|
* In microsoft#1455 I missed making absolute lowercase. * In microsoft#1408 a lot of whitespace was missed leading to output like error: building vtk:x64-linux failed with: BUILD_FAILEDSee https://learn.microsoft.com/vcpkg/troubleshoot/build-failures?WT.mc_id=vcpkg_inproduct_cli for more information.
* In #1455 I missed making absolute lowercase. * In #1408 a lot of whitespace was missed leading to output like error: building vtk:x64-linux failed with: BUILD_FAILEDSee https://learn.microsoft.com/vcpkg/troubleshoot/build-failures?WT.mc_id=vcpkg_inproduct_cli for more information.
@autoantwort points out that it makes sense for those to be clickable.
He also wants us to drop the note: prefix from newlines if we aren't attached to a tty; I'm not sure if that is correct.