http://bugs.winehq.org/show_bug.cgi?id=19018
Summary: [wishlist] Winetricks should be integrated into winecfg Product: Wine Version: 1.1.22 Platform: All OS/Version: All Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: pablomme@googlemail.com
It would seem like a very good idea to integrate the settings offered by the separate winetricks utility into the wine configuration tool, winecfg. There are very basic things (like font smoothing and other direct registry tweaks) in winetricks that one would expect to find in the default configuration tool (and indeed, there are some which are duplicated, like the 'winver' setting). The downloading of alternate DLLs would make a very nice addition to the 'DLL overrides' section of winecfg.
To me, this seems a rather natural thing to do to improve configurability and user experience. Perhaps the winetricks developers would be interested in doing the integration?
http://bugs.winehq.org/show_bug.cgi?id=19018
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Platform|All |Other Resolution| |WONTFIX OS/Version|All |other
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2009-06-21 00:17:25 --- winetricks is not, and will never be an official part of Wine.
http://bugs.winehq.org/show_bug.cgi?id=19018
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2009-06-21 00:17:39 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=19018
--- Comment #3 from Austin English austinenglish@gmail.com 2009-06-22 01:20:25 --- The whole point of winetricks is that it does things that wine itself can't, for technical/legal/etc. reasons.
For instance, it implements hacks to work around bugs (dotnet20, volnum, etc.), and can install things that requires a windows license (art2kmin, etc.).
BTW, the winetricks developers *ARE* wine developers ;-).
http://bugs.winehq.org/show_bug.cgi?id=19018
--- Comment #4 from pablomme@googlemail.com 2009-06-22 06:32:10 --- Thanks for the info. I understand that there may be policies against allowing automatic installation of additional libraries for which you need a license, and that is sensible. However there are some "tricks" which are of a different nature,
- There are "tricks" which amount to minor registry hacks (fontsmooth-*, fakeie6, ...). In my opinion it makes a lot of sense to have these in winecfg. - There are "tricks" which install free software (gecko, firefox3, vlc, ogg, [mono?], ...). Software installation is surely more cumbersome to handle than registry hacks, but there are no licensing issues for these.
Do the above sound like worth making an exception for (especially the simple registry ones)?
http://bugs.winehq.org/show_bug.cgi?id=19018
--- Comment #5 from Austin English austinenglish@gmail.com 2009-06-22 11:01:48 --- (In reply to comment #4)
Thanks for the info. I understand that there may be policies against allowing automatic installation of additional libraries for which you need a license, and that is sensible. However there are some "tricks" which are of a different nature,
- There are "tricks" which amount to minor registry hacks (fontsmooth-*,
fakeie6, ...). In my opinion it makes a lot of sense to have these in winecfg.
Hacks by definitions don't belong in wine.
- There are "tricks" which install free software (gecko, firefox3, vlc, ogg,
[mono?], ...). Software installation is surely more cumbersome to handle than registry hacks, but there are no licensing issues for these.
Gecko should be handled at the packaging level. The others aren't bundled with windows, nor should they be bundled with wine. You don't need, e.g., vlc to run most applications.
The best solution is for package maintainers to bundle a recent winetricks.
http://bugs.winehq.org/show_bug.cgi?id=19018
--- Comment #6 from pablomme@googlemail.com 2009-06-22 11:21:05 --- (In reply to comment #5)
Hacks by definitions don't belong in wine.
Ok, that's bad wording on my part. Call them 'registry operations'.
Gecko should be handled at the packaging level. The others aren't bundled with windows, nor should they be bundled with wine. You don't need, e.g., vlc to run most applications.
Good point. Disregard the program installation stuff then.
However I still believe that the registry operations do have a legitimate place in winecfg. Using your argument: the ability to use ClearType is a setting in Windows - shouldn't 'fontsmooth-*' be a setting in winecfg?
(Sorry about the insistence, I just want to make sure I get my points across.)
The best solution is for package maintainers to bundle a recent winetricks.
Thanks, I'll try to open a request at that level instead.
http://bugs.winehq.org/show_bug.cgi?id=19018
--- Comment #7 from Austin English austinenglish@gmail.com 2009-06-22 12:19:56 --- (In reply to comment #6)
However I still believe that the registry operations do have a legitimate place in winecfg. Using your argument: the ability to use ClearType is a setting in Windows - shouldn't 'fontsmooth-*' be a setting in winecfg?
That setting probably should be, yes. I'm not sure off hand why it's not. IIRC, not all builds of wine support it, depending on your fontforge build.
-
wine-bugs＠winehq.org