Shachar Shemesh <[EMAIL PROTECTED]> writes: > 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.
I don't think so - judging from the directory structure it is specific to this app. > 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. Thought of that, of course, but that is more dangerous: /opt/<app>/wine-config/etc is system-wide and thus works for all users. I restrict myself to modifying on the fly the copy in the user's $HOME. Looks like one more case when what is essentially a single-user system is forced to work in a multi-user environment... :-( > 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. No, but once again, I am only mucking around with (what looks like) an application-specific copy of system.reg. Thanks again, Shachar, -- Oleg Goldshmidt | [EMAIL PROTECTED] ================================================================= 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]
