On Sun, Apr 09, 2000 at 06:24:28PM +0200, Ove Kaaven wrote:
> There's now one FIXME in wineinstall, regarding installing the global
> registry. Wanting to fix it, I looked for ways to actually do it. Now, I
> could just copy the ~root/.wine/system.reg and ~root/.wine/wine.userreg to
> $sysconfdir/wine.systemreg and $sysconfdir/wine.userreg in wineinstall,
> but this may not be what users really want. I'm thinking that if an
> administrator wants to install some piece of software on his system for
> everyone else to use, then he would just log in as root, install it, and
> then the global registry should just reflect the installed software.
>
> I tried symlinking, but neither direction worked...
>
> If I symlinked from $sysconfdir to ~root/.wine, there's this:
> drwx------ 9 root root 1024 Mar 30 19:48 root
> (permissions)
>
> And if I symlinked from ~root/.wine to $sysconfdir, then the symlinks
> just gets replaced with ordinary files when root saves the registry.
>
> What should the installer do?
Hmm,
when root saves the registry:
Why do the symlinks get replaced ?
I assume that is happening because it's the temp file mechanism in the
registry code that is responsible for saving the registry, no ?
And as we don't append to a reg file, but create a *new* temp file and
rename it (AFAIK, I didn't look at the code), symlinks are treated in a
really bad way, i.e. they are thrown away :)
Maybe we really might want to use your proposed "symlink from $sysconfdir
to ~root/.wine" approach, so maybe we might want to fix that temp file
"problem" somehow.
Andreas Mohr
