Hi<br><br><div class="gmail_quote">2010/3/31 Marius Vollmer <span dir="ltr"><<a href="mailto:marius.vollmer@nokia.com">marius.vollmer@nokia.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">ext Robin Burchell <<a href="mailto:viroteck@viroteck.net">viroteck@viroteck.net</a>> writes:<br>
<br>
> Things as I understand it:<br>
> - Qt 4.5 on Maemo5 had no API/ABI compatibility guarentees.<br>
> - Qt 4.6 took liberal advantage of that to change and fix some rather<br>
> suboptimal parts.<br>
<br>
</div>This might have been handled better, though, with a proper soname change<br>
etc. There are ways to cleanly break an interface, still painful, but<br>
at least sterile.<br>
<br>
<br>
In general, I think it is not useful to release an SDK update earlier<br>
than the OS. The way they are joined at the hip, they need to be<br>
released together. (Yes, in an parallel universe, SDK and OS would be<br>
more independent. But they are not and we should not pretend they are.)<br>
<br></blockquote><div><br>I think it's good to able to test that your applications are working with the upcoming version so there's a chance to have less broken packages when the actual update comes. Anyway, time between these releases (SDK and OS) is already too long.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It is of course better to release earlier than later. Thus, if we want<br>
to release the SDK early, we simply need to release the OS with it, as a<br>
beta.<br>
<br>
But even if there is a SDK release with a corresponding OS beta release,<br>
I'd say it should not be installed in the Extras autobuilder. People<br>
can try out the new SDK and OS beta by themselves, we don't need to<br>
force them to use it. The Extras autobuilder should build for the most<br>
recent release of the OS.<br></blockquote><div><br><br>This brings up a question: Is there a need for one more repo? Something like extras-experimental that could have these pre-released updates, etc. for devs to test and play with. The current extras chain (devel->testing->extras) would be only used with the current SDK only.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
(In my dreams, the OS updates would be developed in extras-devel as<br>
well, end-users would eventually SSU from extras, and the SDK as such<br>
would not exist. We would still have the problem of how to make a<br>
binary that is compiled against Qt 4.6 run with Qt 4.5, but everybody<br>
except us has that figured out.)<br></blockquote><div><br>-Timo<br><br></div></div><br>