> Don't ask Qt to switch to it until you've done that work. Tbh, we wouldn't if this post hasn't almost stated that you are pulling the plug. As I saw it: qbs folks have finally started doing the correct thiing (that is - tutorials) and what you are speaking of had a chance to happen. But as of right now no amount of tutorials will change the fact that reluctance to swtich to a new system will become reluctance to change to a _stillborn_ system.
By pulling the plug Lars ensures that qbs has not had a chance and _will not have_ that chance. Oh, and also, maybe we need a separate post about this issue: "Should QBS stay?" Or something like that so that it's visible on it's own and more people jump into the discussion. So far we have quite a few projects in the spreadsheet I created. I wonder how many more will be added. On Wed, Oct 31, 2018 at 12:27 AM Thiago Macieira <thiago.macie...@intel.com> wrote: > On Tuesday, 30 October 2018 13:56:45 PDT NIkolai Marchenko wrote: > > > and has enough of a track record of a community to ask for help. > > > > You quite literally have the system's developer in house. > > Why do you even need to rely on the community so much? > > I'd understand if qbs was an external tool, but that's not the case. > > Because it's a sign of maturity. If the only people who can solve any > problem > are the handful of people who work for the company that developed it, we > have > a serious Bus Factor problem. And guess what? It's exactly what's > happening > right now. > > Ossi and several others are right that qbs was never given a proper > chance. It > hasn't. > > The only thing I'm criticising is that its proper chance involves Qt being > the > guinea pig. Find someone else instead and grow your community. Get track > record for building, cross-compiling, working with weird set ups, > containerised build environments, build farms, etc. Don't ask Qt to switch > to > it until you've done that work. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > > > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development >
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
