-
Notifications
You must be signed in to change notification settings - Fork 359
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
Add winsymlinks:native to the CYGWIN environment variable when running a Cygwin executable on Windows #5793
Conversation
In somewhat haste, nothing's been fixed in OCaml (nor is ever likely to be), so I believe the code is still needed. The stubs are still there, they are called |
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.
Thanks for looking at this! The part in OpamProcess
is completely orthogonal - that's all to do with getting the escaping of arguments correct. It doesn't destructively change CYGWIN
though - it's editing it (in what's looking to me 9 years later to be a possibly over-pedantic fashion, but perhaps the rules for specifying options in the CYGWIN
variable used to be more strict).
Regardless, it's definitely not interfering because my local workaround has been to set CYGWIN=winsymlinks:strict
in my shell prior to invoking opam
and it's not overriding it 🙂
8a49cff
to
48a9665
Compare
@dra27 done |
A thought which didn't occur to me before - does this also apply when we're running commands from within opam (e.g. quite critically, |
ah i think you're right. That code should be in |
48a9665
to
115c065
Compare
…ling a package on Windows Co-authored-by: David Allsopp <david.allsopp@metastack.com>
115c065
to
9f400e4
Compare
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.
lgtm, thanks!
Fixes #5782Actually no, at least not yet. Upon creating the PR I realized another point in the code also modifies
CYGWIN
(in a destructive manner)@dra27 I’m reading the comments for
OpamProcess.cygwin_create_process_env
and the use ofwin_create_process
(which i’m also realizing does not exist in OCaml >= 5.0, which means opam can’t be compiled on Windows if you’re using ocaml 5) and I’m not sure if it’s just a relic of the past that can now be replaced byUnix.create_process_env
or not? Was the issue encountered withUnix.create_process_env
ever got fixed or was it only an issue in opam and thus not something that could actually be fixed upstream?If it is a relic of the past I’ll go ahead and remove it and together with the current code, it should work.