Hi
AS i sent to the -quiet bug, i'm attaching here my message for this bug
thanks
higuita
--- Begin Message ---
hi
> > > Please note that wmi-client is different from winexe. Upstream for
> > The version at git://winexe.git.sourceforge.net/gitroot/winexe/winexe
> This code doesn't have anything to do with wmi - it uses the svcctl
> DCE/RPC interface (not WMI) to start an executable on the remote
> machine. Merging it won't help with WMI support.
But the problem is that we dont have wmi-client in debian and
also don't have winexe, so we don't have any way to interact with a window
machine remotely.
Right now, its a mess, i and many people on debian must rely
on hand compiled packaged, that can break any day with the debian
updated/upgrades and forces the user to search thru many the dead pages
and links to find a pre-build package (that the last time i tried,
they don't work anymore in recent distros) or the source and compile
(if the user knows how).
The full wmi-client is useful, but most people can survive with
just the winexe and a few scripts on the windows side (using the WMIC
client ) for those needing WMI. Winexe is GPLv3 and can be included in
debian without any problem.
Samba4 is the final target, but i still didnt understand if they
have included the winexe patch or not... until its released, the external
winexe is what most people require.
Maybe what is needed is forgetting the wmi-client and create a
new package with the winexe. If the wmi-client change the license, we can
drop the winexe and re-add the wmi-client.
When samba4 is released, the winexe package should be checked and
will be probably removed (or start using to the samba4 code) if already
included the winexe functionality.
So my suggestion is to package the winexe from sf.net, its the
best package we have (it works and have the right license) to solve
the main issue here.
higuita
--- End Message ---
