On 10/24/2010 11:13 AM, [email protected] wrote:
________________________________________
From: Thiago Macieira [[email protected]]
Sent: Saturday, October 23, 2010 6:48 PM
Harri:
I propose, that we don't specify softfp as the baseline for complience,
but rather say that current softfp is temporary phase and we will move
to hardfp as soon as possible, potentially in 1.1 update if we will have
such a thing.
I think that's a bad idea. We can't switch to hardfp without a full binary
compatibility break. So it should be done at the new release, 1.2.
That also means devices upgrading from MeeGo 1.1 to 1.2 will need a full
reinstall/flashing. No applications from any repository or store will survive
and need to be recompiled.
I think that we are not supposed to break binary compatibility between
Meego 1.1 and 1.2 , so breaking at 1.2 is not good option at all ...
So, in this case I propose that we do that in MeeGo 1.1.1 (or whatever is
the right number for MeeGo 1.1 update).
Imho, that will be the least painfull way for everybody, especially if we
decide and communicate this now. Now the amount of code/applications
that needs to be recompiled is still manageable. As well as the number of
affected parties.
I don't think this can be done at all.
this will break all 3rd party apps and components, including codecs,
plugins etc etc
that's not something that's just ok to do easily or.. well really, ever.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
