https://bugs.documentfoundation.org/show_bug.cgi?id=69043
Mike Kaganski <mikekagan...@hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Hardware|x86-64 (AMD64) |All
Keywords| |difficultyInteresting,
| |easyHack, skillPerl,
| |skillWindows
--- Comment #20 from Mike Kaganski <mikekagan...@hotmail.com> ---
It could be fixed, actually. We could add an action to stop the Windows Search
service when managing the ooofilt component.
For that, we need to add "ServiceControl" table [1] to our MSI; it should look
like this in our generated IDT directory:
ServiceControl Name Event Arguments Wait Component_
s72 s50 i2 S50 I2 s72
ServiceControl ServiceControl
StopWindowsSearchService WSearch 34 1
auto_winexplorerext_lib_ooofilt__libreofficedev7_program_shlxthdl
The "auto_winexplorerext_lib_ooofilt__libreofficedev7_program_shlxthdl" is the
ID of the component installing ooofilt.dll, which implements the indexing of
ODF files. Since this ID is generated dynamically, this table also should
generate dynamically: similar to Component, etc. See
solenv/bin/modules/installer/windows/component.pm and
solenv/bin/modules/installer/windows/featurecomponent.pm for examples.
The requirement to stop the "WSearch" service needs to be in some SCP file,
possibly in scp2/source/winexplorerext/registryitem_winexplorerext.scp. This
would incidentally mean that the component on which the ServiceControl entry
depends would be registry_g_m_o_winexplorerext_libreofficedev76.
The change would introduce a new key added to respective SCP item, which would
define the service name, and what to do with it (stop, on install and
uninstall, in this case). The value should be handled in a new .pm file, to
generate the IDT file dynamically.
[1] https://learn.microsoft.com/en-us/windows/win32/msi/servicecontrol-table
--
You are receiving this mail because:
You are the assignee for the bug.
