Wine Traffic #62 For 25�Sep�2000
Table Of Contents
This is the 62nd release of the Wine's kernel cousin
publication. It's main goal is to distribute widely what's
going on around Wine (the Un*x windows emulator).
Mailing List Stats For This Week
We looked at 73 posts in 186K.
There were 30 different contributors.
16 posted more than once.
16 posted last week too.
The top posters of the week were:
- 7 posts in 27K by David Howells <David.Howells@nexor.co.uk>
- 7 posts in 24K by Francois Gouget <email@example.com>
- 7 posts in 12K by Alexandre Julliard <firstname.lastname@example.org>
- 6 posts in 12K by Eric Pouech <Eric.Pouech@wanadoo.fr>
- 5 posts in 12K by gerard patel <email@example.com>
- Full Stats
Archive Link: "RFC: Wine Documentation"
Jeremy White,�Alexandre Julliard,�,�codeweavers
Jeremy White put out for comment an RFC covering the Wine
documentation aspects. This follows the first steps already made (see
BROKEN KCREF). Jeremy wrote:
Jeremy then provided a link to such an experimental
Then, Jeremy proposed some changes in the way documentation is
handled; basically, he was keen on having a separate CVS tree
dedicated to documentation. Alexandre Julliard strongly preferred to
keep the source and documentation trees together, so that changes to
the code are reflected to the documentation.
Dimitrie O. Paun even suggested to move documentation related to a
given DLL into a specific subdirectory of the DLL source. Dimi felt
this had several advantages:
As part of the Wine 1.0 effort, we've been working on improving the
We have a proposal for a way to overhaul the documentation system,
and we'd like some feedback.
We start with the following goals:
- Documentation should be easy to find
- Documentation should be clear (the user should quickly see
the thing that he or she wants, and there should be no confusion
as to which document is 'right')
- Documentation should be consistent (the documentation should
look the same whether it is on winehq or on a mirror, or in
- Documentation should be easy to change.
We propose the following visible changes:
- Entry documentation page should be simplified
- Many multiple disconnected (but similar and/or redundant)
documents should be merged under a consistent format.
- Centralize all of the documentation under one CVS point,
possibly as a new CVS tree, possibly just as the
documentation/ branch of the Wine CVS tree.
- Switch the FAQ to use a FAQ-O-MATIC, to facilitate
updates and changes to it, and to allow the creation of a
world editable late breaking bugs section.
No final agreement seems to have been reached.
- greater probability of having the docs maintained
- easier for people to get into the project
- possibility to maintain the dll separately
Network broadcast issues
Archive Link: "sendto() broadcast works on Windows without a Gateway..."
James Hatheway,�Alexandre Julliard,�
James Hatheway ran into some networking issues:
The app that I am debugging from time to time sends broadcast
(255.255.255.255) UDP packets using the winsock function sendto(). On
Windows, if the default gateway is not configured, the sendto()
function still sends the UDP packet onto the local network. In Linux,
if no default gateway is set, sendto() fails with a "network
unreachable". Since it is possible to have an isolated local network
that isn't connected to the internet, I guess it is possible to not
have a gateway configured, so I want to fix WSOCK32_sendto() to be
like Windows and handle this.
Alexandre Julliard didn't like the proposed fix, and rather suggested to
report an explicit error to the user, asking him/her
(ed.  I do
need to be politically correct) to add an explicit route from
255.255.255.255 to the local network.
New Wine configuration tool
Archive Link: "wine-cfg 0.3b available"
Martin Pilka announced:
It's still an early beta version, so all your comments are welcomed.
This is the first implementation of the tool defined earlier on (read
BROKEN KCREF for the details).
Archive Link: "bug tracking system"
Doug Ridgway,�,�codeweavers,�Douglas Ridgway,�Codeweavers
Douglas Ridgway announced:
Even if it's not fully operational yet, you can still have a look at it.
Codeweavers has been kind enough to set up a new bug tracking system
for Wine using Bugzilla. This will replace the old system. You can see
a preview at
, which is supposed to be
fully live and the official bug database by the end of this week.
The old system is currently only accessible at
and has 500+ existing reports. I can't guarantee that this system will
remain accessible beyond the end of the week. It might be worthwhile
trying to make sure that important reports are copied into the new
system before they are lost / made inaccessible.
A big thank you to Codeweavers for setting up and maintaining this new
system. Good bug tracking is a crucial part of making Wine great, and
this system promises to be a significant improvement over what it's
Sharon And Joy