Re: Possibility of getting an up-to-date version of Wine into Squeeze

[Ove Kaaven <ovek@arcticnet.no>]

Den 21. aug. 2010 10:55, skrev Stephen Kitt:
> On Sat, Aug 21, 2010 at 04:02:37AM +0200, Ove Kaaven wrote:
> > Den 21. aug. 2010 03:01, skrev Svante Signell:
> > > Please take this request seriously. Even if Squeeze is frozen,
> > > distributing the same version (1.0.x) of Wine as Lenny does not look
> > > good! People are trying to help out!
> >
> > I wouldn't hold much hope. These are the options:
> >
> > 1. Get wine-gecko built on Debian. Apparently gcc-mingw32 4.4.4 did
> > not solve all the problems with it, gcc-mingw32 would apparently
> > have to be upgraded all the way to 4.5.0 to build a fully working
> > package. Not sure if the release team will accept that, and even if
> > they did, packaging Wine 1.2 for squeeze will, by now, be a rush job
> > that may result in a package with serious problems.
>
> Have you had a chance to take a look at my packages?  I took the time
> to separate each patch out so that you'd be able to integrate them
> into your git tree without to much trouble.

I'll take a look when the time comes. Until gcc-mingw32 is updated, 
there's not much that can be done anyway.

Note that I already did some preliminary work a while ago (including a 
complete wine-gecko package, just waiting for a working compiler), and 
have had some long-term plans for the Wine package itself, and probably 
not in the direction you might expect or have worked on. So I might not 
have use for such patches, but we'll see when it finally becomes 
possible to update Wine.

For now, I suggest working on a working gcc-mingw32, if anything.

> Note that building wine-gecko also requires an updated version of
> mingw-w64 (used to produce an updated replacement for
> mingw32-runtime).

My own wine-gecko package does not need this. (Though if mingw32-runtime 
were to be updated, its build system could be simplified a bit, I guess.)