[wpkg-users] re the post: WPKG Server 1.1.0 breaks packages working in 1.0.4

Rainer Meier r.meier at wpkg.org
Thu May 28 21:47:05 CEST 2009


Hi Charles,

Charles Gargent wrote:
> re the post: WPKG Server 1.1.0 breaks packages working in 1.0.4
> 
> I have experienced this error also. I have done some investigation,
> this command fails when it used to work in 1.0.4:
> 
> <install cmd='"%software%\WinMerge\WinMerge
> v2.12.2\WinMerge-2.12.2-Setup.exe"
> /LOADINF="%software%\WinMerge\WinMerge
> v2.12.2\WinMerge-2.12.2-Setup.inf" /VERYSILENT /NORESTART' />
> 
> however if you take the spaces out of the path names and remove the
> inner quotes it works here is the working command (notice the
> underscore in the path)
> 
> <install cmd='%software%\WinMerge\WinMerge_v2.12.2\WinMerge-2.12.2-Setup.exe
> /LOADINF=%software%\WinMerge\WinMerge_v2.12.2\WinMerge-2.12.2-Setup.inf
> /VERYSILENT /NORESTART' />
> 
> also here is another way of making it work if you want to keep the
> spaces you haver to escape the quotes
> 
> <install cmd='cmd /c """"%software%\WinMerge\WinMerge
> v2.12.2\WinMerge-2.12.2-Setup.exe"""
> /LOADINF="""%software%\WinMerge\WinMerge
> v2.12.2\WinMerge-2.12.2-Setup.inf""" /VERYSILENT /NORESTART"' />
> 
> Is there some way of tweaking the source code so we can keep this the
> same as 1.0.4, id rather not remove all spaces in the path or escape
> all the quotes.

Well, I am quite sure this is related to the STDOUT/STDERR flushing code (more a
work-around) added in the exec() method of WPKG. The reason and a long trace of
discussion can be found on Bugzilla (Bug 155). Due to the broken functionality
of WSH it's not possible to handle it properly. So I decided to revert these
changes and go back to WPKG 1.0-style behavior.

Please try revision 75 of WPKG available here:
<http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/1.1/wpkg.js?view=log>


Please report if it works for you now (again).

br,
Rainer



More information about the wpkg-users mailing list