Re: WINE registry structure

[Shachar Shemesh]

Oleg Goldshmidt wrote:
In general, I realize that. What seems to be going on on this system
though is that a particular app, on invocation, copies a system.reg
that lives in /opt/<app>/wine-config/etc (*not* in /etc/wine) to the
user's $HOME/.<app>/.wine, and I only operate in
$HOME/.<app>/.wine/system.reg. The app is a singleton, i.e. only one
instance (per user) can run at a time.
 

But the wine configuration is global to that user. If another wine 
application is running at the same time, both this application of yours 
/and/ your changes will break.

Why it is done this way I have no idea.
I have a guess. Wine configuration used to be pretty difficult to 
bootstrap. It was generally easier to copy in a working configuration. 
With recent versions, however, merely running a wine app for the first 
time will create a default registry, drive mapping and directory 
structure prior to running your app for the first time. There is even a 
GUI app (called winecfg) to change these settings (those not changeable 
via regedit or a control panel applet), and in the near future it may 
actually be able to write out the changes..... :-)

I am only hacking the bloody
thing to make the file associations behave in a sane manner (don't
ask). I definitely don't want to learn winelib or regedit for this
purpose. Hopefully I'll do a working prototype and let others bother
about foolproof implementation.
 

So long as you are aware of the risks. This text file is a database, and 
mucking about with it directly is mucking about with a database format. 
It's ok to do if you understand the structure (not too difficult, 
thankfully, for wine's registry) and the DB is down (more of a pitfall). 
Do keep in mind that, by default, all wine applications will use the 
same configuration.

Also, a simpler and less risky solution, why not just run the app once, 
use regedit to modify the keys to whatever it is you want, shut down 
wine, and place the "system.reg" you have instead of 
/opt/<app>/wine-config/etc? At the very least, you can diff the two and 
run "patch" from your script.

I wonder though if the fact that the system behaves as described makes
the situation a bit less perilous.
 

Very fragile, that's for sure. You failed to mention whether that was 
the only wine app any user is likely to ever run, for one thing.

Thanks again for your help,
 

No problem.
         Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]