Re: [Development] Repository Request: qt/licensing

2018-05-24 Thread Thiago Macieira
On Thursday, 24 May 2018 16:18:22 -03 Stottlemyer, Brett (B.S.) wrote: > 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

Re: [Development] Repository Request: qt/licensing

2018-05-24 Thread André Pönitz
On Thu, May 24, 2018 at 12:58:43PM +, 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:

Re: [Development] Repository Request: qt/licensing

2018-05-24 Thread Thiago Macieira
On Thursday, 24 May 2018 09:58:43 -03 Kai Koehne wrote: > 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 Uh... not really. I use git while on the plane :-) -- Thiago

Re: [Development] Repository Request: qt/licensing

2018-05-24 Thread Kai Koehne
> -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? >

Re: [Development] Repository Request: qt/licensing

2018-05-24 Thread Kai Koehne
> -Original Message- > [ ..] > Would it perhaps be possible for configure to just look in "well known" > locations in the system where the online installer can place them (or place a > file > that contains the path to licheck) ? That's a good idea, though the online installer has always

Re: [Development] Repository Request: qt/licensing

2018-05-24 Thread Thiago Macieira
On Wednesday, 23 May 2018 14:49:06 -03 Stottlemyer, Brett (B.S.) wrote: > 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: >

Re: [Development] Repository Request: qt/licensing

2018-05-23 Thread Stottlemyer, Brett (B.S.)
On Wednesday, May 23, 2018 9:43 AM Thiago Macieira wrote: > On Wednesday, 23 May 2018 10:31:17 -03 Kai Koehne wrote: > > Well, the whole point of the exercise is to allow customers to > > configure Qt under commercial terms from git, so any non-shared git module > > doesn't help. > > You can

Re: [Development] Repository Request: qt/licensing

2018-05-23 Thread Thiago Macieira
On Wednesday, 23 May 2018 10:31:17 -03 Kai Koehne wrote: > > In your internal infra, use a different repository branched off from the > > public one, containing the licence checker binary and anything else you > > may need. This repository should never be shared. > > Well, the whole point of the

Re: [Development] Repository Request: qt/licensing

2018-05-23 Thread Simon Hausmann
qt-project.org > > Subject: Re: [Development] Repository Request: qt/licensing > > > > On Friday, 18 May 2018 18:18:02 -03 Thiago Macieira wrote: > > > > Just for clarification: The official source packages contain the > > > > licheck executables already.

Re: [Development] Repository Request: qt/licensing

2018-05-22 Thread Thiago Macieira
On Friday, 18 May 2018 18:18:02 -03 Thiago Macieira wrote: > > Just for clarification: The official source packages contain the licheck > > executables already. My aim is that a git checkout and the source packages > > we provide contain the very same content. > > I understand, but I'm asking you

Re: [Development] Repository Request: qt/licensing

2018-05-18 Thread Thiago Macieira
On Friday, 18 May 2018 12:53:00 PDT Kai Koehne wrote: > > From: Development on > > behalf of Thiago Macieira > > > > > > Is the source code for licheck going to be added to the repository? > > No, I'd only add the

Re: [Development] Repository Request: qt/licensing

2018-05-18 Thread Kai Koehne
te a repository relative to qtbase. Kai From: Stottlemyer, Brett (B.S.) <bstot...@ford.com> Sent: Friday, May 18, 2018 4:45:20 PM To: Kai Koehne; development@qt-project.org Subject: Re: [Development] Repository Request: qt/licensing On 5/18/18, 10:36 AM, "

Re: [Development] Repository Request: qt/licensing

2018-05-18 Thread Kai Koehne
> From: Development on > behalf of Thiago Macieira > > Is the source code for licheck going to be added to the repository? No, I'd only add the binaries. > If not, then the binary cannot be added to the a Qt

Re: [Development] Repository Request: qt/licensing

2018-05-18 Thread Thiago Macieira
On Friday, 18 May 2018 07:36:37 PDT Kai Koehne wrote: > Hi, > > I'd like to request the creation of a repository "qt/licensing" on > codereview.qt-project.org. This will become an optional git submodule of > qtbase (checkout: qtbase/licensing). > > The repository will contain the Licenses and

Re: [Development] Repository Request: qt/licensing

2018-05-18 Thread Stottlemyer, Brett (B.S.)
On 5/18/18, 10:36 AM, "Development on behalf of Kai Koehne" wrote: Hi, I'd like to request the creation of a repository "qt/licensing" on codereview.qt-project.org. This will become an optional

[Development] Repository Request: qt/licensing

2018-05-18 Thread Kai Koehne
Hi, I'd like to request the creation of a repository "qt/licensing" on codereview.qt-project.org. This will become an optional git submodule of qtbase (checkout: qtbase/licensing). The repository will contain the Licenses and binary files (licheck*) that are so far only in our commercial