On Wed, 2008-05-28 at 04:53 -0700, Ch?? Kristo wrote: > First of all I am not exactly clear on how these things are done officially > as there is no documentation on os.org (not that I can find anyway) as to how > a community is proposed. My understanding that a community is a precursor to > a project...feel free to guide me in the right direction. > > What I am proposing: > A community focused on running Wine on OpenSolaris and it's derivitaves > (Belenix, Indiana, SXDE and so on). This proposal includes related open > source technologies such as Wine-Doors. > > What is Wine?, sourced from Wikipedia: > Wine is a software application which aims to allow Unix-like computer > operating systems on the x86 architecture to execute programs written for > Microsoft Windows. Wine also provides a software library known as Winelib > which developers can compile Windows applications against to help port them > to Unix-like systems. > > How will this benefit the OpenSolaris community and in particular the desktop > community?: > The OpenSolaris community and Sun Microsystems are reaching out to developers > by positioning OpenSolaris as a desktop development platform. Many developers > use their systems also as a desktop platform and need to use the same > applications as their Windows using colleagues. The most common being > applications like Photoshop or Visio. > > Support: > Link: http://www.opensolaris.org/jive/thread.jspa?threadID=48261&tstart=0 > This was proposed in the discuss community but it looks like it didn't get > any attention as it wasn't proposed in the Desktop community > > Resources: > WineHQ: http://winehq.org/ > Wine-Doors: http://www.wine-doors.org/wordpress/ > Codeweavers: http://www.codeweavers.com/ > Blastwave wine: http://www.blastwave.org/wine/ > +1 from me.
I'm the current maintainer of the Wine package in SFE and work closely with the Wine developers, and I'd love a central place to gather information on issues specific to Wine on OpenSolaris. A community might make more sense than a project with a specified schedule and deliverables. SFEwine has the most current set of patches for Wine. These work around some important bugs related to OpenSolaris on Wine's Bugzilla right now, as well as some additional functionality that is missing. Bob: I believe the patches on the Blastwave site are current for the version that is in binary form on Blastwave (also Wine is LGPL rather than GPL). BTW, using Wine-Doors is discouraged by the Wine developers as it makes problematic changes to the default Wine configuration. I would suggest against supporting that software until it has ironed out its own issues. -Albert
