svn commit: r47016 - head/en_US.ISO8859-1/htdocs/news/status

Benjamin Kaduk <[email protected]>
Newsgroups gmane.os.freebsd.devel.cvs.doc
Message-ID <[email protected]>
Author: bjk
Date: Sun Jul 19 18:38:42 2015
New Revision: 47016
URL: https://svnweb.freebsd.org/changeset/doc/47016

Log:
  Add the Wine report from David Naylor ([email protected]).

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2015-04-2015-06.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-04-2015-06.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2015-04-2015-06.xml	Sun Jul 19 13:54:43 2015	(r47015)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-04-2015-06.xml	Sun Jul 19 18:38:42 2015	(r47016)
@@ -2576,4 +2576,100 @@
       </ul>
     </body>
   </project>
+
+  <project cat='ports'>
+    <title>Wine/&os;</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Gerald</given>
+	  <common>Pfeifer</common>
+	</name>
+	<email>[email protected]</email>
+      </person>
+
+      <person>
+	<name>
+	  <given>David</given>
+	  <common>Naylor</common>
+	</name>
+	<email>[email protected]</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="http://wiki.FreeBSD.org/Wine">Wine wiki</url>
+      <url href="http://wiki.FreeBSD.org/i386-Wine">Wine on amd64 wiki</url>
+      <url href="http://www.winehq.org">Wine homepage</url>
+    </links>
+
+    <body>
+      <p>This quarter has seen seven updates to the
+	<tt>wine-devel</tt> port that closely tracks upstream
+	development as well as updates to its helper ports
+	(<tt>wine-gecko-devel</tt> and <tt>wine-mono-devel</tt>):</p>
+
+      <ul>
+	<li>Stable releases: 1.6.2 (1 port revision)</li>
+	<li>Development releases: 1.7.40 through 1.7.46</li>
+      </ul>
+
+      <p>The <tt>i386-wine-devel</tt> port has packages built for amd64 for
+	&os; 8.4, 9.1+, 10.1+ and CURRENT.</p>
+
+      <p>Accomplishments include:</p>
+
+      <ul>
+	<li>Rename <tt>wine-compholio</tt> to
+	  <tt>wine-staging</tt> (to match upstream developments).</li>
+      </ul>
+
+      <p>Future development on Wine will focus on:</p>
+      <ul>
+	<li>Add the <tt>getdirentries(2)</tt> patch to the wine-devel port.</li>
+	<li>Redevelop and upstream the <tt>getdirentries(2)</tt> patch.</li>
+	<li>Redevelop and upstream the kernel32 <tt>Makefile</tt> patch.</li>
+	<li>Add support to the <tt>i386-wine</tt> port for pkg 1.5 (library
+	  conflicts currently prevent support).</li>
+	<li>Add support for WoW64:
+	  <ul>
+	    <li>Reduce the <tt>i386-wine</tt> port to just the components
+	      required for WoW64.</li>
+	    <li>Rename the <tt>i386-wine</tt> port to
+	      <tt>wow64</tt>.</li>
+	    <li>Make the wine ports depend on the wow64 ports when built
+	      on amd64.</li>
+	    <li>Investigate and verify the interactions between Wine64
+	      and WoW64.</li>
+	    <li>Investigate possible update approaches for the
+	      wow64 ports (that have to be pre-compiled) and how updating
+	      with the wine ports will work.</li>
+	  </ul>
+	</li>
+      </ul>
+
+      <p> Maintaining and improving Wine is a major undertaking
+	that directly impacts end-users on &os; (including many
+	gamers).  If you are interested in helping please contact us.
+	We will happily accept patches, suggest areas of focus or have
+	a chat.</p>
+    </body>
+
+    <help>
+      <task>
+	<p>Open Tasks and Known Problems (see the
+	  <a href="http://wiki.FreeBSD.org/Wine">Wine wiki</a>)</p>
+      </task>
+
+      <task>
+	<p>&os;/amd64 integration (see the
+	  <a href="http://wiki.FreeBSD.org/i386-Wine">i386-Wine wiki</a>)</p>
+      </task>
+
+      <task>
+	<p>Porting WoW64</p>
+      </task>
+    </help>
+  </project>
 </report>
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/svn-doc-all
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.