InstallDLL & UninstallDLL - explanation and aliases

[mirkobrombin]

To implement the DLL Manager we basically need to:

• copy a DLL from an external location, to an internal one (usually system32/syswow64 but can also be other)
• register a key (which should be now possible thanks to Implement RegistryManager #2)

In the Bottles Next scenario, the wofklow should be the following (writing it as much complete as possible):

• server uses its components downloader to fetch the package
• server uses its overlays manager to create the new layer, then place the DLLs files in the right path
• server start WineBridge and ask to register those DLLs in the registry
• WineBridge perform the changes in the registry
• server ask to reboot
• WineBridge emulate the reboot

I am keeping the collecting step (collecting changes in the overlay, plus the registry diff) on purpose, since out of context here.

--

So, what we need are 2 aliases functions:

1. one that perform the registry key registration for the DLL
2. one that perform the registry key removal for the DLL

[cyberphantom52]

Should DLL manager be part of winebridge?

Winebridge runs inside the prefix but DLL manager will need access to files outside of prefix. Yes, we can access rest of the filesystem inside a prefix but i think it would be better if instead we add API to create/delete/modify files inside a prefix using winebridge and then use that in the component downloader.

Or we can skip the API part and let server place the files in the positions directly.