I am currently using cygwin and using noacl on everything but "/" in fstab.
Yet I occasionally find a file with mangled acls. I can correct things but
it is annoying and disconcerting not knowing how the situation comes about.
Plus I am wary that I might inadvertently mess up a substantial chunk of
some file hierarchy someday.
I am re-considering msys2. I use Cygwin for scripting - no compilations so
cygwin is overkill for my needs.
Will switching to Msys2 eliminate acl weirdies?
I think I would feel safer if there were a msys2 master switch that forces
only Windows ACLs and disables POSIX acls.(Ditto for Cygwin also for that
matter)
I see that launchers are a separate issue not apparent when using Cygwin.
Currently I run a CMD and type bash to start a shell.
I also use assoc and ftype plus PATHEXT so I can easily call shell scripts
from windows command line or CMD/BAT scripts.
e.g.
ftype bsh="C:\cygwin64\bin\bash.exe" %1 %* (I hope I the
most would be to force a -rcfile?)
assoc .sh=bsh
For any script abc.sh in my bin directories, I link it to abc so that it is
seen as executable from a bash or a CMD.
Will launcher-related considerations be required?
I use a wide variety of tools in scripts - are all the Cygwin tools relevant
to scripting available in MSYS2?
I appreciate the ease of cygwin's setup pgm to manage packages. Is there an
equivalent for msys2?
Thanks.
Michel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Msys2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/msys2-users
