Hi Ray, Many thanks for feedback.
On Wed, Aug 12, 2015 at 3:49 AM, Ray Donnelly <mingw.andr...@gmail.com> wrote: > See the comment from "Kitty" on > http://www.hanselman.com/blog/AptGetForWindowsOneGetAndChocolateyOnWindows10.aspx > This is the danger of binary repackaging. We shouldn't promote malware > or systems that deliver it. I would rather wait until AppVeyor adds > MSYS2 support than add MSYS2 to chocolatey. Good advice. > > Sure! Make a pull request to MSYS2-packages, perhaps in a folder > called continuous-integration/AppVeyor I think you missed my pull request mentioned above, I don't might mention again ;-) https://github.com/Alexpux/MSYS2-packages/pull/319 (Seems not a good idea to write long mail, heh) I already put most scripts I need in the ./appveyor folder, I can move them to ./continuous-integration/AppVeyor if you like, but the original location would be easier for me. > Some suggestions: > > 1. Ideally we need separate reports from each of the 4 different > variants, {x86_64, i686} * {MINGW-packages, MSYS2-packages}. Of course > for MSYS2 packages you'd need to run a i686 MSYS2 and a x86_64 MSYS2. > For the MINGW-packages, you'd need to run the build from x86_64 MSYS2 > twice, once as "MINGW_INSTALLS=mingw32 makepkg-mingw ...", then as > "MINGW_INSTALLS=mingw64 makepkg-mingw ..." > No problem, I can improve my script to support them. > 2. If we can identify the following issues distinctly that would be awesome: > 2.1. Unclean patches (grep the log for things such as "patch > unexpectedly ends in middle of line", "Hunk #1 succeeded at 2560 with > fuzz 1.") > 2.2. Patch failures. > 2.3. Build failures separate to check failures. > For 2.3, you can do a build with --nocheck, but I'm not sure if it's > possible to then run just check without rebuilding! Hopefully there's > at least a hacky way to do this. Possible, I think I can give them a try. > 3. Saving the logs somewhere would also be useful for users who > encounter build failures could compare theirs logs against. I don't > know if this is possible. Those logs are already saved to Amazon S3 clould storage by default, anyone could browse the history from https://ci.appveyor.com/project/fracting/msys2-packages/history -- Regards, Qian Hong - http://www.winehq.org ------------------------------------------------------------------------------ _______________________________________________ Msys2-users mailing list Msys2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/msys2-users
