On 05.6.2015 г. 19:52, Enrico Tröger wrote:
On 29/05/15 11:00, Thomas Martitz wrote:
Msys2 is a successor to msys which offers a unix-like environment on Windows combined with a pacman-based package manager. [...]
My standard test:
[D:]grep 00A0 uni*.uni grep: uni*.uni: No such file or directory
[D:]grep 00A0 uni\*.uni grep: uni*.uni: No such file or directory
Why?..
[D:]grep 00A0 uni/*.uni uni/10646-1.uni:00A0 ...
It's actually an *improvement* over MSYS, which required UNI/*.UNI (i.e. a short name if the short and long names are identical).
I don't know about pacman, but the 20MB maintenancetool.exe does not look like something that can be used to manage the MSYS2 components. Out of the box, only "Remove all components" works; the "Default repositories" are empty and read-only, and I can't even see a list of the installed MSYS2 components. Not very impressive, compared against mingw-get, which is < 200KB (.exe + guimain.exe).
Hopefully, this enables us to eventually remove the Waf build system in the longterm.
I'm using waf under Linux as well, since it keeps the source tree clean, and allows compiling only selected plugins without a super-long list of --disable-plugin-s.
Also note that MSYS2 by itself does not include any development stack. Not even a make, like MSYS.
-- E-gards: Jimmy