[cw-discuss] Crossover Games?

[Alexandre Julliard]

Graham <grahamtodd2 at googlemail.com> writes:

> A fork generally is a bad idea.  It diffuses the focus of a project; it
> duplicates resources; it draws people from one area to another.  And so
> a possible fork in the Wine project needs to be flagged, and pose the
> question:is this proposal a good idea?

No, and there is absolutely no reason that the Wine project would be
forked. Windows supports both games and office applications in the same
codebase, and Wine does exactly the same and will continue to do so.

In fact there is a lot of overlap between features required for games
and for office apps; games use standard APIs for things like file
access, networking, html rendering etc. and office apps increasingly use
games features like copy protection, visual effects, sound, etc.
Forking the project would only lead to a huge duplication of effort.

> So unless Codeweavers can give me an assurance that there is ONE
> development project for Wine and no other, no matter how many Wine
> "versions" are produced, unless the resources are to be used for
> development of the same project, I do think there's a chance of a fork.

There is only one development version of Wine used for all Crossover
releases, and maintaining that version is already more than enough work,
it wouldn't make any sense for CodeWeavers to fork the project. Besides,
all our changes are returned to Wine where they will get merged into a
single codebase, so a fork would be doomed anyway.

-- 
Alexandre Julliard
julliard at codeweavers.com