<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 12/15/2010 09:11 PM, Ville M. Vainio wrote:<br>
<span style="white-space: pre;">> On Tue, Dec 14, 2010 at 4:47
PM, Thomas Perl <a class="moz-txt-link-rfc2396E" href="mailto:th.perl@gmail.com"><th.perl@gmail.com></a> <br>
> wrote:<br>
> <br>
>> Wasn't one of the advantages of the SSU to be able to
update<br>
>> single packages from official repositories if need be?
Would it be<br>
>> possible to provide updated (and fixed) packages of Qt
4.7 and Qt<br>
>> Mobility through the official channels as a
single-package SSU, as<br>
>> opposed to doing a PR1.4 (which probably requires
building of new<br>
>> images as well)? This way, users and developers just need
to<br>
>> update through the<br>
> <br>
> QtM yes, Qt no (because Qt is part of the core set of
applications).<br>
> <br>
> The only way to update Qt currently would be to make yet
another <br>
> "hotfix" hack that does dpkg-divert for all the libs. Or,
install a <br>
> new Qt alongside the system Qt (as done by various
-experimental <br>
> packages).<br>
> </span><br>
<br>
The SSU is able to upgrade system packages, that's the whole point
of it,<br>
and QtM can indeed be upgraded through extras(-devel).<br>
<br>
<span style="white-space: pre;">>> dependencies on them and
what not. If Nokia is really not <br>
>> interested in releasing any updates for Maemo 5, we
should better <br>
>> focus on empowering the Fremantle Community SSU and
releasing fixed<br>
>> Qt packages through that channel, and make sure that
everyone uses<br>
>> the Community SSU. This would be more sane, cleaner and
less <br>
>> confusing than the<br>
> <br>
> Problem with community SSU is, does it have enough resources
for <br>
> testing and development? We still got tons of "normal" N900
users <br>
> (those probably are not reading maemo-community) that are not
<br>
> interested in switching to a community ssu - and risk
breaking <br>
> elementary stuff. IIUC it's still a pretty small effort,
without so <br>
> much as a mailing list.<br>
> <br>
> A "service pack" would be a safe thing for developers to
depend on, <br>
> as it would keep the device mostly on the beaten path. Not
much <br>
> development work would go into it, just bare essentials
needed for <br>
> tolerable operation.<br>
> <br>
> Such a service pack can only get us so far, so a full blown<br>
> community SSU is needed eventually - going forward, I would
be<br>
> surprised if we didn't have most of the meego stack &
applications<br>
> working on maemo5 (but still have hildon-home etc).<br>
> <br>
>> Please, no more dirty workarounds and hacks. Just push Qt
+ Qt<br>
> <br>
> Dirty workarounds and hacks are what can be done right now.</span><br>
<br>
Not really, a working SSU is what should be done right now.<br>
If any dirty workarounds have to be done, I would've removed Nokia's<br>
repositories from the trusted list in HAM's configuration file and
announced<br>
the SSU long ago.<br>
Sadly, no one's offering to help with it, might as well start
reading all of<br>
HAM's source to see what goes where and why.<span
style="white-space: pre;"></span><br>
<br>
Regards,<br>
Mohammad Abu-Garbeyyeh<br>
</body>
</html>