http://bugs.winehq.com/show_bug.cgi?id=1372
andi@rhlx01.fht-esslingen.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW everconfirmed|0 |1
------- Additional Comments From andi@rhlx01.fht-esslingen.de 2003-04-06 15:30 ------- a) Because users use root WAY too often. It's a counter-measure. b) because wineinstall configures the Wine environment for a *specific* user. (a Wine configuration is not "global") Thus you need start with this specific user, and when it wants to install the Wine files on your system, you are supposed to provide the root password.
Why am I told to run wineinstall as root to generate a global wine.conf (if I refuse to make a local one), when wineinstall refuses to be ran as root?
Hmm, if it still says that, then it's a bug. A global wine.conf is deprecated. Yep, it's a bug.
Finally, why can't wineinstall be incorporated in: make install?
Because make install shouldn't do what wineinstall does. And the other way around. make install simply installs the compiled Wine files on the system, whereas wineinstall is a "one size fits all" for lazy users which configures everything down to the kitchen sink :-)
Confirming, since wineinstall still talks about wine.conf
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://bugs.winehq.com/show_bug.cgi?id=1372. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.