Versions & mass-appeal

Andreas Mohr andi at
Wed Oct 30 07:45:17 CST 2002

On Wed, Oct 30, 2002 at 12:21:51PM +0200, Shachar Shemesh wrote:
> Ender wrote:
> >    - Getting the right set of dlloverrides and registry entries correct
> >for a large portion of software is irritating. Most of this comes down to
> >the lack of WINE being able to dynamically run RunOnce and wininit.ini
> >entries. Doing this manually is far beyond your average user who just
> >wants to install a reasonably complex program. Something like Crossover's
> > is needed.
> > 
> >
> I'm willing to tackle that (the BiDi stuff is only slowly going, and 
> there may be some unexpected development coming that is outside my 
> hands, so I have SOME free resources available).
> Where do I get to have a look? Either that, or can someone 
> answer a few questions regarding it?
I've been having a finished implementation of wineboot in my tree for ages.
I guess it's about time to get it submitted...

> - When are the boot time activities taking place? On wine start? On 
> wineserver start?
Good question. I guess we once agreed on it being done on winelauncher script
(or alternatively really on user desktop login, but I'm not sure whether this
is what we want)
winelauncher should probably check whether any of the places that register
reboot activities need processing, and if this is the case, then first
finish a wineboot process, *then* start regular wine apps.
All this would have to be resistant against race conditions, of course :-\

> - When are login time activities taking place?
> - How should a reboot request be treated? Should it be an indication 
> that all these operations should start now, and let other wine programs 
> carry on as usual?
IMO we need to make sure we only do this when no other wine process
is running.
Optionally there could be some way to tell Wine to do it immediately,
even during a session, though.

Sounds like nobody ever watched the wineconf2002 streams, since nobody ever
knows about wineboot...

The Declaration of Software Freedom:

More information about the wine-devel mailing list