Re: [Development] Qt6 repo

2021-01-14 Thread Oswald Buddenhagen
On Thu, Jan 14, 2021 at 02:08:43PM +, Volker Hilsheimer wrote: Nevertheless, federating the declaration of the dependencies across modules out to each module is the right idea, I think. no, it's not. for tightly bound co-evolving packages, the vcs should provide as much atomicity as reason

Re: [Development] Qt6 repo

2021-01-14 Thread Nibedit Dey
Thank you again everyone for the suggestions. Most people have agreed that there is a need for simplifying the repo nomenclature, build system, and scripts. This will attract contributions from more Qt developers. People who have been using Qt for years are familiar with the submodules, and the scr

Re: [Development] Qt6 repo

2021-01-14 Thread Volker Hilsheimer
> On 14 Jan 2021, at 16:12, Thiago Macieira wrote: > > On Thursday, 14 January 2021 06:08:43 PST Volker Hilsheimer wrote: >>> Same here. Please refrain from cooking up our own git submodule >>> replacement soup. >> >> Hm, but dependencies.yaml already *is* our own “git submodule replacement >> s

Re: [Development] Qt6 repo

2021-01-14 Thread Thiago Macieira
On Thursday, 14 January 2021 01:50:57 PST Volker Hilsheimer wrote: > $ ninja tst_class_I_fixed_check > > and ninja rebuilding everything that needs to be rebuilt across all modules > before running the test is a huge timesaver. And I learnt yesterday: $ ctest -L cbor Test project /home/tjmaciei/

Re: [Development] Qt6 repo

2021-01-14 Thread Thiago Macieira
On Thursday, 14 January 2021 06:08:43 PST Volker Hilsheimer wrote: > > Same here. Please refrain from cooking up our own git submodule > > replacement soup. > > Hm, but dependencies.yaml already *is* our own “git submodule replacement > soup”, to some degree, isn’t it? Not if I don't care about t

Re: [Development] Qt6 repo

2021-01-14 Thread Thiago Macieira
On Thursday, 14 January 2021 01:28:46 PST Christian Kandeler wrote: > On 1/13/21 11:46 PM, Thiago Macieira wrote: > > Like I said above, the latest tip of the branch for every single > > module. This > > recipe has worked for me for 10 years. > > I don't believe you. It has. Just one detail: I'v

Re: [Development] Qt6 repo

2021-01-14 Thread Volker Hilsheimer
> On 14 Jan 2021, at 08:21, Nibedit Dey wrote: > > Thank you everyone for the suggestions. > I posted in the development group as there was less participation on the > topic in the interest group. > Below are my suggestions: > • Create a clean qt6 supermodule for better maintainability. It

Re: [Development] Qt6 repo

2021-01-14 Thread Volker Hilsheimer
> On 14 Jan 2021, at 13:50, Joerg Bornemann wrote: > > On 1/13/21 5:28 PM, Thiago Macieira wrote: >> On Wednesday, 13 January 2021 05:37:21 PST Volker Hilsheimer wrote: >>> * stop using git submodules >>> >>> Using them serves no real purposes anymore. We anyway have our own scripting >>> in for

Re: [Development] Qt6 repo

2021-01-14 Thread Joerg Bornemann
On 1/13/21 5:28 PM, Thiago Macieira wrote: On Wednesday, 13 January 2021 05:37:21 PST Volker Hilsheimer wrote: * stop using git submodules Using them serves no real purposes anymore. We anyway have our own scripting in form of init-repository to avoid that people have to deal with that stuff.

Re: [Development] Qt6 repo

2021-01-14 Thread Eike Ziller
> On Jan 14, 2021, at 11:08, Volker Hilsheimer wrote: > >> On 13 Jan 2021, at 22:58, André Pönitz wrote: >> >> On Wed, Jan 13, 2021 at 12:48:45PM -0800, Thiago Macieira wrote: >>> On Wednesday, 13 January 2021 10:17:02 PST André Pönitz wrote: I have a product that depends on qtbase, qtde

Re: [Development] Qt6 repo

2021-01-14 Thread Alex Blasche
> -Original Message- > From: Development On Behalf Of > Volker Hilsheimer > > I am not asking for *support*. I am asking how to find a recent > > working combination of Qt modules that I need for porting some code > > base to Qt 6. Don't tell me to use 6.0 nor to wait for some 6.x. > >

Re: [Development] Qt6 repo

2021-01-14 Thread Edward Welbourne
Volker Hilsheimer (14 January 2021 10:50) wrote: > The init-repository script does some extra work that is supposed to > give people a leg up though, such as setting up commit hooks and > remotes in all submodules. It also provides mechanisms for selecting what set of modules you want checked out.

Re: [Development] Qt6 repo

2021-01-14 Thread Volker Hilsheimer
> On 14 Jan 2021, at 10:49, Benjamin TERRIER wrote: > On Thu, 14 Jan 2021 at 08:21, Nibedit Dey wrote: > Thank you everyone for the suggestions. > I posted in the development group as there was less participation on the > topic in the interest group. > Below are my suggestions: > • Create

Re: [Development] Qt6 repo

2021-01-14 Thread Volker Hilsheimer
> On 13 Jan 2021, at 22:58, André Pönitz wrote: > > On Wed, Jan 13, 2021 at 12:48:45PM -0800, Thiago Macieira wrote: >> On Wednesday, 13 January 2021 10:17:02 PST André Pönitz wrote: >>> I have a product that depends on qtbase, qtdeclarative and qttool, and >>> qtdeclarative and qttools refer to

Re: [Development] Qt6 repo

2021-01-14 Thread Volker Hilsheimer
> On 13 Jan 2021, at 17:28, Thiago Macieira wrote: > > On Wednesday, 13 January 2021 05:37:21 PST Volker Hilsheimer wrote: >> * stop using git submodules >> >> Using them serves no real purposes anymore. We anyway have our own scripting >> in form of init-repository to avoid that people have to

Re: [Development] Qt6 repo

2021-01-14 Thread Benjamin TERRIER
On Thu, 14 Jan 2021 at 08:21, Nibedit Dey wrote: > Thank you everyone for the suggestions. > I posted in the development group as there was less participation on the > topic in the interest group. > Below are my suggestions: > >- Create a clean qt6 supermodule for better maintainability. It's

Re: [Development] Qt6 repo

2021-01-14 Thread Christian Kandeler
On 1/13/21 11:46 PM, Thiago Macieira wrote: Like I said above, the latest tip of the branch for every single module. This recipe has worked for me for 10 years. I don't believe you. Christian ___ Development mailing list Development@qt-project.org