[maemo-developers] QT Packages, Repositories and PR1.2

[From: Attila Csipa]

On 5/20/10, Felipe Crochik
<felipe at crochik.com<h/1tqlt06b4so7k/?v=b&cs=wh&to=felipe at crochik.com>>
wrote:
> Isn't the Qt version on PR 1.2 supposed to be 4.6.2 (the same we have on
> qt4-maemo5 and scratchbox right now)? I can't remember where I read this
but

No way of knowing until PR1.2 actually hits the streets. The version
in the SDK *is* newer than the libqt4-maemo5 one (note - it is the
same base qt version, 4.6.2, but contains additional fixes/changes).
Note that the PR might touch on other things, too - for example the
4.6 on PR1.1 does not support autorotation, has hildon banner coloring
issues, etc. So there are things that work or look differently even
with the same Qt version.

> package but I would feel better if it was not as simple as submitting a
new
> package with the same name and higher version. Maybe a consent from the
> maintainer or at least a "put package on hold" for few days waiting for a
> reply (or lack of) from the maintainer to an email sent automatically from
> maemo informing of the change. As now, It all can happen too quickly, in
> less than a day someone can submit a package and this package will be
> available to the users that have the development catalog. Just my paranoid
> self talking... As the community grows it may become more important.

I will talk about this to maemo.org people to see what the options are.

> The issue is not developing for an upcoming version. We will always have
the
> scenario where there is a stable/official version and a upcoming one.
Right
> now we have the qt4-core (4.5) and the qt4-maemo5 (4.6) in two different
> folders... Everything would be fine if the qt packages included with pr1.2
> were the qt4-maemo5 once out they would simply replace the "beta" ones
>
> I may be too naive but I think all this could be much simpler if we just
had
> each official/major release of qt as a different package and installed to
a
> different folder. Developers would be able to control the application
> dependencies. In fact that is exactly what I think my suggestion would do
> now.

Now we're gettingto the crux of the matter. The choice is not to
support all versions of Qt simultaneously, but to have a single base
version for each PR, and have this version on the NAND for speed
reasons IIUC (plus integration issues as mentioned above) - and also
to lower memory footprint, having GTK+ and Qt simultanously is
stressful enough, having multiple versions of Qt in memory would make
things even worse. So you won't have Qt4.5 on PR1.2, no Qt4.6 in the
PR that will hopefully bring us Qt4.7, etc. The devel version is there
just for, well, development and testing. As you can see this
significantly lowers our maemo.org maneuvering space, too...

Best regards,
Attila
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.maemo.org/pipermail/maemo-developers/attachments/20100521/7c54b8a3/attachment.htm>