-
Notifications
You must be signed in to change notification settings - Fork 22
Windows fixes #41
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
Windows fixes #41
Conversation
dra27
left a comment
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.
#40's on its way in, so you can rebase without that commit with a few bits and bobs here there. Definitely skip Cygwin in this part for now - the aim is to spin out Cygwin into a container of its own which we won't maintain here (but which we may well then go on to consume for the mingw/msvc images)
FIXME: move Opam's cold compiler from 4.09 to 4.12
The name of the distro conflicts with multiarch images on Windows which bundle multiple versions of Windows. Microsoft doesn't provide a latest tag either.
Older versions are not build if they're deprecated, an we loose Windows multiarch images.
c55ffe7 to
e4cbcf8
Compare
I used to split the install to recover most of the cache in case of a Docker crash. Now we know crashes were caused by nested virtualization.
FIXME: telemetry can be disabled in newer winget, but that requires modifying some json (which is doable using powershell 6, not 5 because the json doc has comments; but the base image has powershell 5).
Doc: https://github.com/microsoft/winget-cli/blob/master/doc/Settings.md#telemetry The Powershell 5 JSON parser doesn't support comments, which the default settings.json file of WinGet contains. We resort to a hacky hack to add the necessary fields to disable telemetry. Another option could be to pull a JSON parser (e.g., jq, Powershell 6 or 7). The file needs to be generated with `winget settings`. It seems to be encoded in UTF-8 (without BOM) with LF line endings. Powershell 5 doesn't support UTF-8 without BOM, let's stick to ASCII. Running winget settings again validates the settings file.
New batch of fixes!
This in particular duplicates the base Windows image to have mingw and msvc images. The final design still may change.
Incorporates #40.