winewrapper

Dimitrie O. Paun dpaun at rogers.com
Thu Nov 21 16:43:17 CST 2002


On November 21, 2002 05:12 pm, Alexandre Julliard wrote:
> You shouldn't use winewrapper, you should copy wineapploader and adapt
> it to your situation. This is what winemaker is supposed to do too,
> though I think it's somewhat broken right now.

OK, that's better. I don't need winemaker for this, I don't want to
redefine their entire build process. People are are quite attached to
their build process, you know... :)

Now, what I don't like is to ship them that script. There's no need,
really, all they have to do is link to it. And for it to work right
out of the tree, I can just add a small thingy in wineapploader that 
looks at where the symlink is pointing, and tests if a wineserver is
available. We require too many changes in the way people build apps,
and that's no good if we want them to build on Winelib. We got to
keep is real simple, and non-invasive. KISS rules. ;)

Is that acceptable?

-- 
Dimi.




More information about the wine-devel mailing list