-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
[VTK] VTK ExprTk cmake patch #30058
[VTK] VTK ExprTk cmake patch #30058
Conversation
@MonicaLiu0311 this PR is currently blocking #29665 and an upcoming VTK version refresh. |
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 agree with @dg0yt , please do not close and create new PRs with no changes in content, and/or at least describe the history of how the changes got there.
It seems that the patch could be reduced to one line, removing the "2.71828"?
ports/vtk/FindExprTk.patch
Outdated
+ break() | ||
+ endif () | ||
+ endforeach () | ||
+ if (NOT ExprTk_VERSION) |
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.
ExprTk_VERSION
seems to be unused; could you just remove this entirely rather than trying to fix it in a patch?
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.
(To clarify, I don't mean patching this out, I mean just not doing this part of the patch since it seems like nobody is listening to the answer)
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.
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.
Objective is to unblock and merge the following PR: #29665 which has been in limbo for nearly 2 months.
The primary reason for this seems to be an implicit cyclic dependency that comes about due to how vcpkg has been architected.
@BillyONeal : We've gone from an all builds and green ticks to all failures post your proposed changes. As such all your proposed changes will now have to reverted as they fail when being applied to the main VTK cmake.
|
I was saying "these are the changes that should happen in the source"; I agree with @dg0yt that you are intending to search for
Doing things like closing and reopening the PR as a different number makes that situation worse as you go to the back of the queue each time. That PR being blocked for months doesn't alter our responsibilities to be extremely limited in the patches we author because we are not the owners of the code bases in question. (We do not want to create a CVE-2008-0166 / https://wiki.debian.org/SSLkeys situation)
OK, can you download the patch ( |
@BillyONeal that was the very patch I was originally applying, The same one people in other (and this one) PRs keep on preventing said PRs from being merged by requesting changes and needless commons - which I've mentioned over and over again. ToDo: I'm going to close this PR and start a fresh one, Once a successful builds and all green ticks, lets merge it without anymore handwaiving and dramas. @JonLiu1993 hopefully we are in agreement. 👍 |
@ArashPartow, Thanks your PR again, but we really don't agree to frequently close new PRs. This is not only not conducive to your PR being merged as soon as possible, but also increases the workload of CI. I hope you understand. |
@JonLiu1993 I'm happy to continue with this PR - though I'm not sure how it increases the CI workload as the jobs will run on this PR or on a new one so same number of clock cycles either way for every change made to the PR(s). My only concern is that a fresh PR with only 1 comment will be quicker to review/ merge than having others go through all the comments in say this PR to only come to the conclusion that the initial commit was what was needed all along. In any case I'll clean this PR up and hopefully we can get this merged as soon as possible as the following PR: #29665 is still waiting on this PR to be merged. |
Pinging @ArashPartow for response. Is work still being done for this PR? |
@BillyONeal @vicroms , the VTK upstream master currently contains the FindExprTk.patch changes, |
I would be willing to take the patch provided it is demonstrated that upstream is already likely to ship the thing updated soon but build needs to be working first of course :) |
Convert this PR to draft since there is no progress. Please ping us if this PR is ready for review again. |
Closing this PR as it has not been updated for the past few months |
./vcpkg x-add-version --all
and committing the result.This patch is intended to unblock the following PR: #29665
and is based on the following VTK MR: https://gitlab.kitware.com/vtk/vtk/-/merge_requests/9981