On Thursday, May 24, 2018 12:48 AM, André Pönitz wrote: > ... does not mean that I would necessarily appreciate the attempt to access > network at arbitrary times ...
On Thursday, May 24, 2018 11:19 AM, Thiago Macieira wrote: > Uh... not really. I use git while on the plane :-) Fair points. I tend to build/update QtBase only a few times around the new releases, and usually I build/update QtCreator at the same time. Thus given the QtCreator code I referenced previously means those use cases/concerns are broken independent of my proposal. Maybe a combination is possible, where the project files look in a common location. If licheck isn't found, attempt to grab the file via https and put it there? Or print the necessary `git clone` message to grab licheck and put it in the right spot, then error out? Anything that avoids manual steps that are only found in the online documentation. Brett -----Original Message----- From: André Pönitz <apoen...@t-online.de> Sent: Thursday, May 24, 2018 12:48 AM To: Kai Koehne <kai.koe...@qt.io> Cc: Stottlemyer, Brett (B.S.) <bstot...@ford.com>; Thiago Macieira <thiago.macie...@intel.com>; development@qt-project.org Subject: Re: [Development] Repository Request: qt/licensing On Thu, May 24, 2018 at 12:58:43PM +0000, Kai Koehne wrote: > > -----Original Message----- [...] Can .pro files test for commercial > > vs. oss licenses? If so, and you create a non- Qt project repo, > > couldn't some .pro in qtbase retrieve licheck, like QtCreator does > > here: http://code.qt.io/cgit/qt-creator/qt- > > creator.git/tree/qtcreator.pro#n123? > > > > Is that an acceptable solution? Seems like it would work here, > > although I think the time stamp generation and commercial licenses > > would need to be added to qtbase (I think). > > Thanks, that's actually an interesting idea. Obvious downside is that > you need network access ... but you can argue that, if people are > using git, they most likely have it I am not sure I got the context right here, but as a general remark: "being in principle able to access network on demand, with permission, possibly restricted to certain times or other circumstances" does not mean that I would necessarily appreciate the attempt to access network at arbitrary times, in automated ways, possibly without my active knowledge and permission. So I'd prefer a git checkout to be usable offline, completely, without usable network access or even probing. Andre' _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development