Slashdot Mirror

← Back to Stories (view on slashdot.org)

First Release Candidate of Wine 1.0 Released

Posted by ScuttleMonkey on from the come-a-long-ways dept.

moronikos writes to mention that the first release candidate of Wine 1.0 was announced and released into the wild today. This new version includes only bug fixes as the team is in a code freeze while pushing for the full 1.0 release.

10 of 284 comments (clear)

  1. Wait, What?! by aitikin · · Score: 5, Interesting

    I was always under the impression that WINE, based on how it is designed, would never be finished, or even close to a finished release point. I mean, yeah, I know 1.0 doesn't mean it's done, just that it hit a specific milestone, but even so, WINE, being considered a ⥠1.0 version seems to me like it shouldn't happen until it can at least come close to running most everything thrown at it.

    Just my non-developer, non-programer, former WINE-user $.02.

    --
    "Don't meddle in the affairs of a patent dragon, for thou art tasty and good with ketchup." ~ohcrapitssteve
  2. Y'know by Colin+Smith · · Score: 3, Interesting

    When I switched from Windows to Linux, it turned out that I was able to function without specific applications, there are Linux equivalents for pretty much everything.

    --
    Deleted
  3. Re:but... by ardor · · Score: 3, Interesting

    It would be SO ironic if one had to use Wine in Cygwin to play older games in Vista without crashes...

    --
    This sig does not contain any SCO code.
  4. Re:Hooray! Long live Wine 1.0! by Kjella · · Score: 3, Interesting

    I am hoping this version will be treated as a longer lived, stable, supported branch. WINE will never become quite like other software, which define their own features. Think of it like a web browser with lousy standards support (not that the Windows API is anything like a standard), there's really no point in creating a very long-lifed branch that scores 58%. You do some development and you're at 61% and the new version is just better and should replace the old one everywhere. The only real reason to keep a stable branch is to keep people from getting hit with regressions. Because all kinds of software runs on top of WINE, it can have some really bad regressions as applications can go from platinum (runs flawlessly) to garbage (not at all) because it does something in the initialization that failed. So yes, a more stable branch than the biweekly development snapshots is good. Any older branch than say 3-6 months I think will be pretty useless.
    --
    Live today, because you never know what tomorrow brings
  5. Re:but... by TeknoHog · · Score: 3, Interesting

    Finally, for the semantically pedantic: yes, recent versions of Dosbox also have a "dynamic" execution mode which tries to do the same that wine does. Naturally, it only works when running Dosbox on x86-compatible hardware.

    QEMU does this too, as does any decent virtualization system. So emulation means translation between different kinds of hardware?

    --
    Escher was the first MC and Giger invented the HR department.
  6. Wine - an unmitigated SUCCESS! by blind+biker · · Score: 4, Interesting

    Just look at the list of applications supported by Wine and you'll understand why I say that. Basically, if I can run Civ IV, Heroes IV and other strategy games on Linux, and with Matlab having a Linux version, there's very little to justify my using Windows. OK, there's Fruityloops, but that's it!

    --
    "The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
  7. Mac Binaries? by TheRaven64 · · Score: 3, Interesting

    Does this mean they'll start releasing binaries for OS X soon? I've compiled it a couple of times, but it's a lot of effort (you need to check out things from two separate svn repositories, run a script, hunt bugs, then compile for every version), and since they claim in the first paragraph of the front page to support OS X I'd really expect them to have regular binary builds.

    --
    I am TheRaven on Soylent News
  8. Re:Hooray! Long live Wine 1.0! by slimjim8094 · · Score: 4, Interesting

    That's called winegcc, I think. Basically you code your apps to work on Wine and compile it to a native application using that.

    Either Google Earth or Picasa (or both) do that.

    --
    I have developed a truly marvelous proof of this comment, which this signature is too narrow to contain.
  9. Cygwine? by tepples · · Score: 5, Interesting

    but you can run cygwin to get a linux-like environment ;) Some people have used Wine and Cygwin as test cases for each other.
  10. Re:So what's the definition? by paskie · · Score: 3, Interesting

    Would you hold Wine responsible for bugs or use of undocumented internals in the programs that do not run?

    If the applications are wide-spread, for that matter, yes, I would. Wine's point is not to emulate ideal Windows environment but to make Windows apps run on Linux, and if working around bugs in them that don't show in Windows is what it takes too, it should do it. Microsoft also does plenty of regression testing when making new version of Windows, often adding workarounds for widespread older apps - in that case it's controversial but Wine is even more clear-cut here.

    If it's just about implementing the documented APIs, that shouldn't be that hard after all, but that's not where the devil is, I believe.

    --
    It's not the fall that kills you. It's the sudden stop at the end. -Douglas Adams