kde-qt branches after 4.6.0 release

Parker Coates parker.coates at gmail.com
Tue Dec 1 17:49:51 GMT 2009

On Tue, Dec 1, 2009 at 11:50, Dmitry Suzdalev wrote:
> On Tuesday 01 December 2009 19:40:49 Pau Garcia i Quiles wrote:
>> Knowing the "right" branch
>> of kde-qt.git was the whole problem, all the time.
> Ah, right that was another reason, now I recall.
> But still. Is it a real problem? We have mailing lists, we have /topic on irc,
> forums, blogs etc. That is we have a certain set of well known places where
> this information can be published - I mean info about which branch to checkout
> and use.
> The only case I see where this wouldn't work is if some developer doesn't use
> any of these sources, i.e. developer who is disconnected from community :)
> But I expect him to run into some other problem (not only kde-qt) sooner or
> later - from time to time we happen to have certain changes that are announced
> and explained on core mailing lists or irc...

The issue for me personally is that *I* don't really build KDE trunk.
My computer does, with the help of kdesvn-build, at regular intervals.
The way kdesupport and current kde-qt/master work means that I almost
never have to adjust anything manually. When there is a new
recommended version of a dependency, my computer gets it automatically
and builds it before building kdelibs, kdepimlibs, kdebase, etc.

Would it be a big deal to change Qt branches every few months? Not
really, but it is still an inconvenience. That is, unless I teach
kdesvn-build to read the mailing list and deduce the correct branch on
its own. :)


More information about the kde-core-devel mailing list