Let's simply delete the wineinstall script. It's not really needed anymore, it was just there for compatibility.
People have been talking about doing it for some time: http://winehq.org/site/?issue=227#Nuking%20Wineinstall perhaps now's the time.
- Dan
-- Wine for Windows ISVs: http://kegel.com/wine/isv
I've always liked wineinstall, even made a handful of improvements to it. Wineinstall was useful for setting up a default configuration but now that we setup a default configuration automatically with wineprefixcreate it doesn't seem necessary anymore. Users that compile via source should be fine with './configure&&make' and 'make install' like they use to build and install most other programs.
Chris
On Sunday 29 January 2006 11:57 pm, Dan Kegel wrote:
Let's simply delete the wineinstall script. It's not really needed anymore, it was just there for compatibility.
People have been talking about doing it for some time: http://winehq.org/site/?issue=227#Nuking%20Wineinstall perhaps now's the time.
- Dan
-- Wine for Windows ISVs: http://kegel.com/wine/isv
On 1/29/06, Dan Kegel dank@kegel.com wrote:
Let's simply delete the wineinstall script. It's not really needed anymore, it was just there for compatibility.
People have been talking about doing it for some time: http://winehq.org/site/?issue=227#Nuking%20Wineinstall perhaps now's the time.
What does it do that make install or wineprefixcreate can't already do? I haven't used wineinstall in a long time.
-
Chris Morgan -
Dan Kegel -
Jesse Allen