No monolithic binaries in Windows builds?

[mjcarman]

Is it intentional that the last two releases (0.10.0 and 0.11.0) have only included the "msvc" builds (individual binaries for each tool) and not the "gnu" build (monolithic multi-call binary)?

I've been using the latter at work because it's easier to update (via marcosnils/bin; winget is blocked). I've been holding off on updating from 0.9.0 hoping it was just a glitch in the build toolchain, but if it's an intentional pivot I'll have to adjust.

[sylvestre]

Not sure it changed but happy to take a pr to fix it :)

[oech3]

.zip for Windows contains both of individual binaries and milti-call binary (coreutils) because symlinking is uncommon on Windows.
So PR is unnecessary.

[mjcarman]

Ah, thank you! I didn't realize that recent msvc releases included both the individual and multi-call binaries in the same *.zip file.

[sylvestre]

TIL, would it make sense to split the zip into two artifacts ?

[oech3]

I don't want to do that since we already have 19 artifacts...

[sylvestre]

not sure it is a problem :)

[oech3]

I think we can contain coreutils binary and individuals directory at toplevel.