Results 1 to 9 of 9

Thread: Wine 1.2 Hits A Fifth Release Candidate

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    14,658

    Default Wine 1.2 Hits A Fifth Release Candidate

    Phoronix: Wine 1.2 Hits A Fifth Release Candidate

    While there has already been four release candidates in preparation for the Wine 1.2 release, a fifth release candidate has now emerged a week later as their blocker bug list still is not cleared...

    http://www.phoronix.com/vr.php?view=ODM2Nw

  2. #2
    Join Date
    Dec 2008
    Posts
    315

    Default

    Blocker list is getting small. Can't be too much longer.

  3. #3

    Default

    Quote Originally Posted by Hephasteus View Post
    Blocker list is getting small. Can't be too much longer.
    Because a lot of bugs are excluded from it and nominated for the future Wine releases.

  4. #4
    Join Date
    Dec 2008
    Posts
    315

    Default

    Quote Originally Posted by birdie View Post
    Because a lot of bugs are excluded from it and nominated for the future Wine releases.
    Windows can screw up wine at a much faster rate than wine can tame it. I prefer a complete facist approach. Linux or GTFO.

  5. #5

    Default

    To be fair, some of the issues with WINE are because legacy APIs are not well supported:

    http://www.virtualdub.org/blog/pivot/entry.php?id=239

    Software that supports Windows NT 4.0 uses the DirectDraw 3 API, which is not supported by WINE. WINE only cares about DirectX 7 and up, so the oldest version of DirectDraw available is DirectDraw 7:

    http://en.wikipedia.org/wiki/DirectDraw
    http://wiki.winehq.org/DirectX-ToDo


    Allow explicit creation and access of front and back buffers for ddraw interfaces earlier than version 7. Current implementation uses dd7's style and prohibits this, which breaks some games.

  6. #6

    Default

    Quote Originally Posted by Hephasteus View Post
    Blocker list is getting small. Can't be too much longer.
    Very few of the bugs they are fixing in each RC were actually blocker bugs. It seems that most people working on WINE have little interest in fixing the blocker bugs and just want to fix their own things, which makes sense.

  7. #7
    Join Date
    Mar 2009
    Posts
    131

    Default

    What are the chances that we will see a working DIB engine in this release?

  8. #8
    Join Date
    Nov 2008
    Posts
    766

    Default

    Quote Originally Posted by Shining Arcanine View Post
    Very few of the bugs they are fixing in each RC were actually blocker bugs. It seems that most people working on WINE have little interest in fixing the blocker bugs and just want to fix their own things, which makes sense.
    If you take a good, hard look at the blocker bugs, most of them are anything but easy to fix. It's likely most of them will be marked as "damn, still couldn't fix them. Let's just move them to 1.4, maybe they'll magically disappear by then.".

    Really, if they weren't fixed by RC1, most needed changes would be too invasive to include after that, anyway.

    Quote Originally Posted by unimatrix
    What are the chances that we will see a working DIB engine in this release?
    Zero. IIRC there were two working DIB engines, but they were always shut down with "meh, we don't like the design, but we can't be bothered to tell you how to do it right."
    If you google a bit, there's a patchset you can use. If you really need a DIB engine, that is.

  9. #9
    Join Date
    Sep 2008
    Location
    Vilnius, Lithuania
    Posts
    2,542

    Default

    41 left, not that much of an improvement compared to older RCs, but it's getting there. At this rate it would take 4 more RCs to get there, though.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •