[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: advpack: The Plan
From:       Markus Amsler <markus.amsler () oribi ! org>
Date:       2006-03-31 9:17:21
Message-ID: 442CF3A1.7000304 () oribi ! org
[Download RAW message or body]

James Hawkins wrote:

>Internally, there will be three main install functions: install_init,
>which will open the INF, make sure it's legit, and other
>initializations, spapi_install, which will call setupapi to install
>the base INF commands, and adv_install, which will parse the install
>section and run the provided commands.  
>
I'm quite sure RunPreSetupCommands gets executed before the base INF 
commands. I'm not sure wether there are others (BeginPrompt, BackupReg 
comes to mind). So you need two install functions like adv_install_pre 
and adv_install_post.

>This is The Plan so far, so if anyone has any ideas or suggestions,
>I'd love to hear from you.
>  
>
Why not simply use the same mechanism as in setupapi [1]? My patch [2] 
back in january was using it, and it looked like a good idea.

Markus

[1] http://source.winehq.org/source/dlls/setupapi/install.c
[2] http://www.winehq.org/pipermail/wine-devel/2006-January/044083.html



[prev in list] [next in list] [prev in thread] [next in thread]