maemo at csipa
Feb 24, 2010, 6:44 AM
Post #22 of 63
>> How will this PR1.2 change be reflected on the maemo.org dowloads section
>> (i.e. how will it be ensured that the user gets presented the correct
>> install-this link) ?
>A different .install file can be offered based on your browser string.
How are you going to make sure you catch all of them ? For MicroB, okay, but
Firefox, Tear, Midori, whatnot ? Does not really sound like a foolprof
solution (you also need to sync with Maemo Select, and just hope that there
are not too many links floating around) :(
>> Second, is there a safety mechanism considered that will disallow
>> inclusion of 'the other' firmware's repository to prevent potential
>> version-related breakage ?
>There is not a lot we can do there. If a user adds the repository on an
>'old' device, some applications just won't install because dependencies
There are a few more troublesome scenarios that can present themselves - like
if someone adds the old repo, and has a repo-refresh issue with the new one
afterwards (I often have this problem with extras-testing and extras-devel).
In both this and the scenario you mention, H-A-M/apt will prevent downgrades,
luckily, but it's easy to cut off your own upgrade path if you DO manage to
install something from the wrong repo.
>> What happens to apps (especially those with Qt dependencies) _currently_
>> in Extras, i.e., how will they get to the fremantle1.2 Extras repo ?
>The Qt apps are currently blocked from being promoted to prevent issues.
It would be helpful if this would be visible from the testing page, too (not
just for 4.6). I have several Qt4.5 dependent packages in the QA queue
nearing required quarantine delay fulfillment. It's just a waste of tester
and developer time then.
>The fremantle-1.2 repository will probably need to be 'legacy' clean. Qt
>4.5.3 is not available in Extras and will probably not be available on any
>repository enabled by default on the device. This means that applications
>depending on this, will not work.
>Those applications need actual changes to work with Qt4.6 iirc.
Okay, so we basically ditch Qt4.5-compiled applications currently in Extras.
Is the Ovi team aware of this as there are quite a few Qt 4.5 applications in
Ovi repositories,too ? Will they get their fremantle1.2 repo, too (I know,
ask them -> wait for a meaningful response so long that it becomes moot :) )
or will they hope Qt ABI compatibility gets them through ? And if you think
Ovi has no bearing on Extras downloads, take into consideration Firefox is in
Ovi, so if browser string based info is used, it will bite you if it's not
handled in a timely manner :)
maemo-developers mailing list
maemo-developers [at] maemo