On 2002.02.23 23:49 [EMAIL PROTECTED] wrote: > On Sat, 23 Feb 2002, David Elliott wrote: > > > application. Save yourself a lot of trouble trying to figure out where > to > > place a hook in wine and simply write it into a completely seperate > > program. You can then have wine actually run that program with a > > CreateProcess call or similar at whatever point. The code to do this > > should NOT be in the wine emulators source code itself, nor do I > believe > > it should be linked in with it. > > Well, if it is a Winelib program, it would be linked with it, sort of, > and loaded by it, but I think that is not what you mean here, is it?
Err, by "the code to do this" I was still referring to the code that does the bootup procedure. And I don't believe that it should be linked to the emulator. It can and will have to be linked to winelib (thus making it a winelib program) but it should definitely not be linked in with the emulator portion of wine. The emulator may use a CreateProcess to call it during startup, but I would prefer a shell script. [SNIP] > > distributors of Wine to implement the actual policy and only provide > the > > mechanism. This is what Alexandre has been saying, and I am saying the > > same thing. Policy decisions do not belong in Wine, even as > configuration > > options when it can be helped. If you feel you absolutely MUST have > this > > run every time a wine program is started or every time a wine program > > finishes (maybe this would be better) then write a shellscript like so: > > > > #!/bin/sh > > wine "$@" > > wine_movefiles > > > > This is so simple, why would you even waste your time trying to hack it > > into the boot code for wine? > > > > -Dave > > > Right. I like that. > Yeah.. I think that this is a reasonable solution and we let the distributors figure it out from there. -Dave
