William Knopp writes:
What's the story with wine on intel os x?
A few people, including Codeweavers, are working on it. More would be welcome. There is no politics keeping people away, as far as I know. If you run into any developer who says that politics is keeping him or her from submitting patches to wine-patches, please let me know. - Dan
I think you missed my point. I know people are working on it. The problem is "a few people, including Codeweavers, are working on it," which is just about the sum-total of the information out there, is not enough. There is very little information out there for potential developers to know what's going on with wine and intel macos x. For instance, a status page describing to-do items would be a start (I'm going to add it to the wine wiki when I figure out what the status is). It should be mentioned on winehq, so macos x developers know to investigate further when they check wine out. Expecting people to dig through the code or the mailing list is unreasonable. Is this really only obvious to me?
I don't mean to be rude; I just see some easy ways to attract mac people to wine. Wine is likely to be an important addition to mac users' software base in the future. So many people want the "mac experience," but have to run windows software. Many more people, I'd say, than those who wanted the mac experience and the unix software suite, and look at how popular fink is. It's a disservice to both parties to not properly advertise.
On 6/25/06, Dan Kegel dank@kegel.com wrote:
William Knop writes:
What's the story with wine on intel os x?
A few people, including Codeweavers, are working on it. More would be welcome. There is no politics keeping people away, as far as I know. If you run into any developer who says that politics is keeping him or her from submitting patches to wine-patches, please let me know.
- Dan
On 6/26/06, William Knop william.knop@gmail.com wrote:
I think you missed my point. I know people are working on it. The problem is "a few people, including Codeweavers, are working on it," which is just about the sum-total of the information out there, is not enough. There is very little information out there for potential developers to know what's going on with wine and intel macos x. For instance, a status page describing to-do items would be a start (I'm going to add it to the wine wiki when I figure out what the status is). It should be mentioned on winehq, so macos x developers know to investigate further when they check wine out. Expecting people to dig through the code or the mailing list is unreasonable. Is this really only obvious to me?
You could just ask, "Hey, what's the status of Wine on Intel Max OS X?". No one has really stepped up to work on that aspect of Wine, outside of Codeweavers, so there's not a whole lot of incentive to put this information up. So if you're wanting to work on this, step up to the plate, and I'm sure we'll be more than willing to help.
On 6/26/06, James Hawkins truiken@gmail.com wrote:
You could just ask, "Hey, what's the status of Wine on Intel Max OS X?". No one has really stepped up to work on that aspect of Wine, outside of Codeweavers, so there's not a whole lot of incentive to put this information up. So if you're wanting to work on this, step up to the plate, and I'm sure we'll be more than willing to help.
You pretty much directly quoted the first line of his first email. He's also offered to add the status to the wiki once it becomes public knowledge (e.g. when someone from within codeweavers sends an email to the list with a little information).
--tim
On 6/26/06, Tim Schmidt timschmidt@gmail.com wrote:
On 6/26/06, James Hawkins truiken@gmail.com wrote:
You could just ask, "Hey, what's the status of Wine on Intel Max OS X?". No one has really stepped up to work on that aspect of Wine, outside of Codeweavers, so there's not a whole lot of incentive to put this information up. So if you're wanting to work on this, step up to the plate, and I'm sure we'll be more than willing to help.
You pretty much directly quoted the first line of his first email. He's also offered to add the status to the wiki once it becomes public knowledge (e.g. when someone from within codeweavers sends an email to the list with a little information).
Well, I was trying to be nice by not saying that his attitude in his emails tends to put devels off, and emails like that usually get ignored. That's why I said *just*, meaning, only ask that question.
Oh... Sorry about that. I suppose I did come off a bit critical.
Will
On 6/26/06, James Hawkins truiken@gmail.com wrote:
Well, I was trying to be nice by not saying that his attitude in his emails tends to put devels off, and emails like that usually get ignored. That's why I said *just*, meaning, only ask that question.
-- James Hawkins
On Mon, 26 Jun 2006 04:08:30 -0400, William Knop wrote:
Oh... Sorry about that. I suppose I did come off a bit critical.
I think your email was OK, but wine-devel gets a constant stream of Mac users/developers telling us how many Mac users want Wine, how they would be a big benefit to the project, how Apple-land is a land of milk and honey etc ... whereas not many people here are actually Mac users. Telling people that's it's super important won't actually speed anything up.
Not aimed specifically at you, this is just a general trend that's been on the increase lately. You know what they say about wishes and horses ...
thanks -mike
Hi Mike,
On 6/27/06, Mike Hearn mike@plan99.net wrote:
I think your email was OK, but wine-devel gets a constant stream of Mac users/developers telling us how many Mac users want Wine, how they would be a big benefit to the project, how Apple-land is a land of milk and honey etc ... whereas not many people here are actually Mac users. Telling people that's it's super important won't actually speed anything up.
I don't think they are wrong about feeling that the site just seems to totally ignore OS X. I guess the FreeBSD and Solaris guys feel the same way reading over recent discussions. Alexandre does not treat patches from anyone as a second class citizen but the site does seem to be very Linux centric rather than platform agnostic. Like read the Myths page. Its all about Linux. I am happy to rewrite some bits of the site to make it broader in scope.
On 6/27/06, Steven Edwards winehacker@gmail.com wrote:
I don't think they are wrong about feeling that the site just seems to totally ignore OS X. I guess the FreeBSD and Solaris guys feel the same way reading over recent discussions. Alexandre does not treat patches from anyone as a second class citizen but the site does seem to be very Linux centric rather than platform agnostic. Like read the Myths page. Its all about Linux. I am happy to rewrite some bits of the site to make it broader in scope.
That's true, but then what the myths page says could really apply to any "alt" operating system. But writing "Linux/FreeBSD/OpenSolaris/MacOS/BeOS" every time is unwieldy, especially as most of our users are on Linux anyway. I guess you could rephrase it all in terms of non-Windows systems.
Er... I did ask that, and I have stepped up to the plate. :)
Well, I said I'd update the wine wiki with the status, anyway. I also think it'd be a good idea to add to the winehq main page, but I wasn't sure who to talk to:
"Wine provides both a development toolkit for porting Windows source code to Unix as well as a program loader, allowing many unmodified Windows programs to run on x86-based Unixes, including Linux, FreeBSD, Darwin (MacOS X), and Solaris."
Will
On 6/26/06, James Hawkins truiken@gmail.com wrote:
You could just ask, "Hey, what's the status of Wine on Intel Max OS X?". No one has really stepped up to work on that aspect of Wine, outside of Codeweavers, so there's not a whole lot of incentive to put this information up. So if you're wanting to work on this, step up to the plate, and I'm sure we'll be more than willing to help.
-- James Hawkins
On 6/26/06, William Knop william.knop@gmail.com wrote:
Er... I did ask that, and I have stepped up to the plate. :)
Well, I said I'd update the wine wiki with the status, anyway. I also think it'd be a good idea to add to the winehq main page, but I wasn't sure who to talk to:
Good to hear, we can always use more active help. If you want to change the winehq main page, just make a patch and send it to wine-patches@winehq.org. I think the best that you can do about a status update is wait to see if anyone responds to this thread. Unfortunately, most of the work that is needed to get Wine running on Intel Macs can only be done by Alexandre Julliard, unless I'm mistaken. You can send him a line at julliard@winehq.org, or see if he replies to this thread.
I'm personally a relative Noop to Wine on Mac intel development. My goal has been to conquer the threading issues that keep it from running most modern-day apps, but I haven't really found the support (at least from the darwine email lists) necessary to write this component. About the only place there I've contributed was on the have a separate vs don't have a separate email list, which IMHO if they have one PPC should be mentioned as when I see the Darwine project I see it as one aimed at Intel macs, not PPC. That may be the reason that my responses have gone quiet over there -- intel isn't a goal.
Dave
--- James Hawkins truiken@gmail.com wrote:
On 6/26/06, William Knop william.knop@gmail.com wrote:
I think you missed my point. I know people are
working on it. The
problem is "a few people, including Codeweavers,
are working on it,"
which is just about the sum-total of the
information out there, is not
enough. There is very little information out there
for potential
developers to know what's going on with wine and
intel macos x. For
instance, a status page describing to-do items
would be a start (I'm
going to add it to the wine wiki when I figure out
what the status
is). It should be mentioned on winehq, so macos x
developers know to
investigate further when they check wine out.
Expecting people to dig
through the code or the mailing list is
unreasonable. Is this really
only obvious to me?
You could just ask, "Hey, what's the status of Wine on Intel Max OS X?". No one has really stepped up to work on that aspect of Wine, outside of Codeweavers, so there's not a whole lot of incentive to put this information up. So if you're wanting to work on this, step up to the plate, and I'm sure we'll be more than willing to help.
-- James Hawkins
-- David Bialac dbialac@yahoo.com
-
Dan Kegel -
David Bialac -
James Hawkins -
Mike Hearn -
Steven Edwards -
Tim Schmidt -
William Knop