[Development] Qt6 repo

Oswald Buddenhagen oswald.buddenhagen at gmx.de
Thu Jan 14 23:23:32 CET 2021

On Thu, Jan 14, 2021 at 02:08:43PM +0000, 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 reasonably possible.

>It's tradeoff is between (eventual) consistency that allows us to 
>declare a release that includes all packages, and not making a 
>centralized .gitmodules file the bottleneck. The 5 step process that 
>required the qt5.git integrations to succeed twice to make trivial 
>changes in private APIs that were used across modules, is not something 
>I think we want back either.
you're setting up a false dichotomy. i've described how to do it 
properly with only .gitmodules before the .yaml crap went into full 
production, but tqtc was (as usual) more interested in protecting a 
prior investment than doing things right.

and yes, it *is* crap. run gitk --all in any non-central module and tell 
me with a straight face that what you're seeing doesn't suck big time.  
yes, as the maintainer of qttranslations i have to deal with that on a 
(somewhat) regular basis.

More information about the Development mailing list