[maemo-community] "Community service pack"

From: Felipe Crochik felipe at crochik.com
Date: Mon Dec 13 17:05:26 EET 2010
I don't know what the libqt4-bearer-hotfix entails but just saw this thread
few minutes ago on qt devnet:


My last comment was exactly about who is/will be in charge of distributing
the qt packages (the community or nokia)?

It would be great if we could, at least, manage the "experimental" packages
(or have nokia update them very often) so developers could always count on
having the last fixes. Most applications would rely on the "official"
packages but any application that is not critical or that depends on a "fix"
after the last release could depend on the experimental packages. 

Do we have any restrictions on promoting packages that depend on "qt


-----Original Message-----
From: maemo-community-bounces at maemo.org
[mailto:maemo-community-bounces at maemo.org] On Behalf Of Ville M. Vainio
Sent: Monday, December 13, 2010 9:25 AM
To: List for community development
Subject: "Community service pack"

As it appears, there is a wish to deploy various packages to fix known
problems in N900 PR1.3.

Immediately, I'm thinking of two things everyone that expects a
non-broken QML experience should have:

- libqt4-bearer-hotfix
- http://gitorious.org/qtquickcompat

(BTW, explore libqt4-bearer-hotfix package to see how you can use
dpkg-divert to patch things without removing the official PR

Optimally, there would be a PR1.4 providing these, but we are probably
not expecting one in the immediate future ;-).

It would make sense to have a single metapackage
(community-service-pack, or something to that effect) that we would
expect everyone to have installed. Applications that need it could
have it as a dependency, instead of enumerating every
unbreak-my-platform patch ever developed.

This is different from Community SSU in the sense that

1) It would not remove the PR metapackages
2) It would probably be more conservative/boring, shipping little
fixes that can comfortably be done by adding packages, instead of
upgrading the "locked down" ones.
3) It can be easily deployed on people's phones by just having it as a
dependency for your package, instead of making them switch the whole
hog to community ssu.

I would see this metapackage as something that should be moderated by
elected maemo community council.

When the full blown Community SSU gains more foothold, maybe this
won't be needed anymore, but in the mean time a good interim solution
is needed.

Ville M. Vainio @@ Forum Nokia
maemo-community mailing list
maemo-community at maemo.org

More information about the maemo-community mailing list