QT Packages, Repositories and PR1.2

RE: QT Packages, Repositories and PR1.2

Felipe Crochik

2010-05-22 14:25 UTC
Attila,

> Hate to be the bearer of bad news :( What we managed to agree for the
PR1.2 release is that development releases starting with PR1.2 will not be
called libqt4-maemo5 as it's not that obvious that it's *really* just a
version for testing, prone to breakage and not necessarily the exact one
that will end up in the next PR. Future releases will sport the
'experimental' moniker (f.e. libqt4-experimental, python-qt4-experimental)
so it's more clear that it (and stuff depending on it) are not meant to be
promoted to end users. Not ideal, but hopefully will reduce confusion until
a better solution is found that is acceptable for both Nokia and the
community.

I started this subject after reading the post by Venemo
(http://talk.maemo.org/showthread.php?t=52442) so I decided that a good way
to close it would be to add a post there (page 4).

Having threads like that "out in the open" and "our" exchange of emails
remind me of why I wanted the n900 so badly. It is a pretty unique device
and even more unique community. I hope "we" can manage to make it more of a
"mass market" product so nokia can justify maintaining it but, at the same
time, I would hate to have to give in this "geek" feeling to it.

Thanks again,
Felipe

  •  Reply

Re: QT Packages, Repositories and PR1.2

Ianaré Sévi
Karma: 77
2010-05-22 14:30 UTC
Le 22 mai 2010 06:15, Benoît HERVIER <khertan@khertan.net> a écrit :
>>I'll wait a little longer for this to get resolved, but if it takes
>>too long I just might ebay my n900 and go Android.
>
> You can also compile it yourself and create your own repository ...
> easier to manage, and do the trick ... and switch back to the maemo
> repository again when everythings will be fixed.
>

I've already made packages available through the garage, but there are
several problems with doing this :

* No way to promote packages past extras-devel.

* Asking non-technical users to start adding repos should be
discouraged due to security and stability issues. Having a community
reviewed repo is a great thing, if it actually worked as intended.

* I don't want users to have to look through the web to install an
app, it should be listed in the phone's manager.

* Fragmenting apps is a sure way to lose out against iPhone and
Android which do have centralized app managers.

Granted, deployment is not stopped, but going out of our way as
developers to also be package managers is a little silly IMO. Nokia's
expertise as a hardware maker but not a software publisher has been
showing itself lately ...

- ianaré sévi
  •  Reply