@fracting, I'm addressing this message to the mailing list only, but feel free to forward it to the other recipients.
On 5. 6. 2015 12:30, Qian Hong wrote: > While many things work out of box, it is possible that MSYS2 users are not > familiar with Wine, or Wine users are not familiar with MSYS2, so we made a > simple guide for how to use MSYS2 on Wine: > http://sourceforge.net/p/msys2/wiki/MSYS2%20on%20Wine/ It seems that this page (and its source at https://gist.github.com/fracting/d1e2707da9e1790dbe0f) is already out of date, at least regarding which bugs are fixed and which aren't. When you put a new version up, let us know and someone will update the wikipage on SF.net. > I tried wine msys2-i686-20150512.exe /Silent and a few other ways I was > guessing but none works. Is unattended installation supported now? Google > search suggested that IFW Version: "2.0.81" supports unattended installation, > not sure if I miss something or it is not yet supported on the MSYS2 side. If > this could be resolved that will be great appreciated. If you don't care about testing the installer itself, you can always use the .tar.xz package. > - We hope to setup some daily build of important msys2 packages on top of > Wine in Linux server as soon as possible. > > During last 3 upgrade of MSYS2 in the past months, 2 of 3 trigger Wines bug > which prevents bash.exe from start. It was a pain to debug the msys2 runtime > itself because almost no tool works, I really don't want to do that again ;-) > In order to catch new bugs at first minutes, I'm hoping that we can monitor > msys2 runtime git repo (and other repos for important packages), rebuild > these packages every commit, at least every day. If that could be done in > Travis CI then that's perfect, we are still investigating. > Any ideas are welcome! Note that the MSYS2 runtime repository is updated in bursts (by rebasing on top of the Cygwin repository), so continuous builds won't probably help much with locating the offending commit. But! if we're able to get our changes to the build system upstreamed to Cygwin, we could set up a continuous build for their repository, which *could* help with finding problematic commits. > - If we could compile and run the builtin test suite of MSYS2/Cygwin and test > on Wine, that will be very useful. Anyone have good news about compiling the > test suite located in winsup/testsuite? I asked about the testsuite once on #cygwin and it seemed that it's not actively maintained or used. (Maybe it was just that the right person wasn't on-line.) -- David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------
_______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
