On 19/10/10 7:12 PM, "ext Wichmann, Mats D" <[email protected]>
wrote:
> [email protected] wrote:
>> On 19/10/10 6:47 PM, "ext Thiago Macieira" <[email protected]> wrote:
>>
>>> Em Terça-feira 19 Outubro 2010, às 17:31:10,
>> [email protected] escreveu:
>>>> Hi,
>>>>
>>>> For MeeGo 1.2 the X.org 1.10 release is too late. We did not upgrade
>>>> kernel and X in the beginning of the 1.2 cycle because we wanted to
>>>> keep the codeline stable and working. We would not upgrade X in the
>>>> end of the cycle either. That should be pretty clear common sense.
>>>>
>>>> The only solution that I can see is to go with what Thiago proposed
>>>> below. That is a solution which works now in Harmattan. The maintainer
>>>> of the code is open as stated below.
>>>
>>> Thanks for replying Sakari.
>>>
>>> I'll check what we can do to reduce the maintenance burden of the patch.
>>>
>>> This is a bit unfortunate for us since we do need to focus on XInput 2.1
>>> anyway: other teams will not stop because of MeeGo. If they forge ahead
>>> with the development, we need to be a part of it to ensure our needs
>>> are met.
>>
>> Yes - I agree. It is unfortunate but many times the upstream schedules
>> don't match with distro's.
>
> that is certainly true, but can we really afford to have 1.2 without
> "proper touch support" unless we use a dead-end fork that nobody at the
> moment wants to spend time on?
To me it is: a) not MT support or b) inproper MT support. I would suggest to
go with b). Proper support is not possible from the schedule point of view.
>
> this sounds like a pretty big issue to me.
It is.
-sakari
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
