On 25/02/2017 21:03, Ray Donnelly wrote: > It's entirely possible for someone to make a non rolling distribution > from the msys2 repos. You'd set up your own repos and advise people to > switch out our rolling ones for your ones. For it to be appealing you'd > probably want to add some comprehensive tests that all the package > versions you have selected work really well together. > > I somewhat like the idea (*) but it's not something I expect msys2 would > do as we're doing it rolling as we consider it the best way, occasional > breakages and all, and don't have the resources to commit to this > unrolling variant. > > (*) Somewhat because if a significant number of people switched to it > and away from upstream msys2 then bugs would get found less quickly and > msys2 upstream would be less good.
I do not think this is the experience of other projects that provide releases as well as a current (your rolling release), for example Linux distros, the FreeBSD kernel and RTEMS which I am involved with. I suspect at the moment a lot of users avoid updating something that is working because it may break. If a newer version of package is only available on current or a later release users need to update. For the RTEMS Project we would welcome a `stable` view of MSYS2 because it lets us specify something we know works and have tested against. At the moment we cannot do this via the MSYS2 project and I have resisted creating an RTEMS release of MSYS2 with our own repo because I do not want to become a project on its own. An RTEMS user deploying on Windows needs to create a local MSYS2 install or they may end up with a range of different MSYS2 installs depending on when they build each development workstation and if their project is for space flight this needs to be controlled and audited. From the responses so far there looks to be a need and I can be included on that list. With nothing to fill this role those who need this each have to separately create something similar which fragments the effort. It would be nice to have any efforts brought in under the MSYS2 project and governed so the quality that current exists can continue. Which ever way this ends up I will respect the wishes of you and the others who run the MSYS2 project. It is a really great tool and I again thank you. Chris ------------------------------------------------------------------------------ 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 Msys2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/msys2-users
