Dear Ray, I see your point here! Also about the users power in testing. But I would like to add that, for what its worth, my original main goal is to actually aid in msys2 testing in stability improvements.
I think the best value I can add is via another angle for the CI system. Where the current CI has a focus on building only the modified packages (to quickly get a response), I would like to iteratively bootstrap the full system from ground up, in the hope that this will uncover problems in inter-dependencies that might otherwise go unnoticed. As an example, I have until now failed to build a full toolchain when starting from a plain vanilla msys2 installation. This might be due to issues on my side, but at least in some cases I could already provide new insight. Furthermore, I think on every toolchain update, it would be very helpful to test that the new toolchain builds at least as many packages as the previous did (or it better have a good excuse for not doing so :-) In my humble opinion this is a very valuable test, and also some- thing I can actually provide. For what its worth, this could already uncover some problems that could be fixed and pushed upstream. I hope this might address at least some concerns? In any case I would not want to hinder msys development. And all of the praise should go to the developers!!! Thanks for the awesome msys2!!! Cheers, Mario On 25.02.2017 11: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. > > On Feb 24, 2017 4:53 PM, "Daniel Goldman" <dgold...@ehdp.com > <mailto:dgold...@ehdp.com>> wrote: > > Just my two bits. As a user, I would like to have a "tagged release", > similar to how I run ubuntu LTS server for years before upgrading. > > I run msys2 behind a firewall, so the security updates seem not > important. If my firewall is penetrated, everything on my computer would > be affected. I'm looking for a "stable, reproducible work environment". > I would probably not use "rolling releases". > > Of course, it would depend on the size of the distributions, but for > most people, I believe saving disk space is no longer a big concern. > > I have not run into any of the incompatibilities or problems that at > least a few people seem to have reported. Perhaps that is because I have > not updated anything for several years? > > Daniel > > On 2/24/2017 3:13 AM, Mario Emmenlauer wrote: > > > > Dear Matthew Postiff and Daniel Goldman, > > > > This is actually a valuable input that I did not consider before! This > > would enable you to ensure a fixed environment as required i.e. for > build > > and test systems, or for a shared work environment. While I can see good > > arguments for rolling releases (security updates etc), I can also see > > good benefit in tagged releases (stable, reproducible work environment). > > > > > ------------------------------------------------------------------------------ > 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 > <mailto:Msys2-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/msys2-users > <https://lists.sourceforge.net/lists/listinfo/msys2-users> > > > > ------------------------------------------------------------------------------ > 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 > Viele Gruesse, Mario Emmenlauer -- BioDataAnalysis GmbH, Mario Emmenlauer Tel. Buero: +49-89-74677203 Balanstr. 43 mailto: memmenlauer * biodataanalysis.de D-81669 München http://www.biodataanalysis.de/ ------------------------------------------------------------------------------ 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
