re: New Wine Gecko package
James Mckenzie wrote:
It depends on the timeline for the 1.2 release. If this is a long way off, it may be worth the effort.
I don't know. The 1.1 branch has are lots of improvements people want; what's so special about Gecko? IMHO we should leave the 1.0 branch alone, and just get on with 1.2. Speaking of which, I wonder which of Alexandre's 1.2 wish list features will be done first? http://wiki.winehq.org/WineReleasePlan Win64 is looking like the front runner at the moment, but there were some USB patches recently, maybe that will come from behind.
On Fri, Feb 6, 2009 at 3:48 AM, Dan Kegel <dank(a)kegel.com> wrote:
James Mckenzie wrote:
It depends on the timeline for the 1.2 release. If this is a long way off, it may be worth the effort.
I don't know. The 1.1 branch has are lots of improvements people want; what's so special about Gecko? IMHO we should leave the 1.0 branch alone, and just get on with 1.2.
I agree. The potential security issues that have been fixed would (from what I understood) specifically target Wine. Targeting Wine 1.0.1 would be... pretty restricted. I don't think it's worth investing time for something like this when 1.2 is coming soon.
Speaking of which, I wonder which of Alexandre's 1.2 wish list features will be done first? http://wiki.winehq.org/WineReleasePlan Win64 is looking like the front runner at the moment, but there were some USB patches recently, maybe that will come from behind.
I haven't followed recent discussions about it, but it seemed to me the DIB engine got the most efforts and work done lately. If it's accepted and starts being usable, it'd be great JL -- Adys
On Fri, Feb 6, 2009 at 1:11 AM, Jerome Leclanche <adys.wh(a)gmail.com> wrote:
On Fri, Feb 6, 2009 at 3:48 AM, Dan Kegel <dank(a)kegel.com> wrote:
James Mckenzie wrote:
It depends on the timeline for the 1.2 release. If this is a long way off, it may be worth the effort.
I don't know. The 1.1 branch has are lots of improvements people want; what's so special about Gecko? IMHO we should leave the 1.0 branch alone, and just get on with 1.2.
I agree. The potential security issues that have been fixed would (from what I understood) specifically target Wine. Targeting Wine 1.0.1 would be... pretty restricted. I don't think it's worth investing time for something like this when 1.2 is coming soon.
It doesn't really matter if 1.2 is coming soon or not. 1.0.1 is meant to be stable, and backporting gecko 0.9.1 and it's necessary infrastructure doesn't constitute a 'stable' fix/patchset. -- -Austin
participants (3)
-
Austin English -
Dan Kegel -
Jerome Leclanche