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

From: Felipe Crochik felipe at crochik.com
Date: Thu May 20 16:26:46 EEST 2010
I am trying to understand why we can't just upload the qt 4.6 deb files used
by scratchbox to "extras-development" so anybody can easily have access to
applications developed using qt4.6.  I understand that maybe some of the new
"standard" qt4.6 may not work until PR1.2 is out but I haven't seen any
actual reports of anything that doesn't work or works worst than the current
qt4-maemo5 version.

 

Right now, as far as I can tell:

-          If you use the "old" standard 4.5.3 packages you can't use the
new 4.6 features including the maemo5 lib. 

-          If you use the new "standard" 4.6 packages the users won't be
able to install on their devices because they won't have the qt 4.6 until PR
1.2 is out. 

-          If you use qt4-maemo5 packages your application will be blocked
from moving to testing and we will have to submit new packages once PR1.2 is
out.

 

Am I correct on this summary?

 

I saw a thread on talk.maemo.org about adding the repository used by the qt
sdk to get the new qt4.6 but it is very dangerous for most users.

 

Can anybody help me find the answer to these questions?

 

1.	What happens if two people submit packages with the same name to the
"extras-development"?
2.	What happens if a package with the same name exists on different
repositories? 
3.	any other reason (legal, technical, ..) why one of us can't submit
the deb files to extras-devel? Would/could we upload them as non-free to
make easier?

 

I assume that the package dependencies use the package name and version so
if we preserve the qt packages names once PR1.2 is out we would not have any
issues. in fact people would not even have to update them until a new
version is out.

 

Felipe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.maemo.org/pipermail/maemo-developers/attachments/20100520/4428b0a4/attachment.htm>
More information about the maemo-developers mailing list