http://bugs.winehq.org/show_bug.cgi?id=15199
--- Comment #14 from Maciej Pilichowski bluedzins@wp.pl 2008-09-10 13:11:09 --- Maybe my English is failing me :-)
Ok, step by step. Let's say I run rpm -i winexxxx I will get -- wine, winecfg, etc.
So _IF_ there would be a time_machine in Wine environment (or package, or set, or toolbox, or I am out of words), then I would run time_machine
so in this case rpm -i winexxxx would give me not only wine, winecfg, but also time_machine. I would not have to install it separately. And since it would be dealing with internals of wine environment it could use some winelibs.
Yes, I probably can write this tool on my own (and I will try) but the one thing is disturbing me that officially it is not guaranteed to edit registry files (in raw text mode) and only on bugzilla (in other report) I heard that well I could if wine is not running. This looks like some unofficial tricks, so thus is this wish -- if there is some "unofficial" knowledge it would be better to keep it within wine environment (set, package, toolbox, you name it).
Btw. the fact that some utility comes with Wine does not mean it has to be something using Windows API, it could be sh script.