Re: [dev] Windows' unopkg.exe does not differentiate between stderr and stdout, where does stdout go to when piping ?
This is a bug: http://www.openoffice.org/issues/show_bug.cgi?id=102854 --Joachim Rony G. Flatscher wrote: Hi there, experimenting with OOo 3.2's unopkg.exe (under WindowsXP, SP3) it seems, that the output from unopkg.exe is only directed at stdout, whereas under Linux error messages (like given package not installed and the like) are directed to stderr, and normal messages to stdout. Is this intentional or a bug? Furthermore, trying to pipe normal output to grep seems to not work, i.e. something like: unopkg list --shared | grep CACHE would not work on Windows, but would under Linux (i.e. display the lines containing the string CACHE). (Yes, I made sure that the string is output as a result of running unopkg list --shared. The grep I am using on Windows is: GNU grep 2.5.3.) Actually, the following does not work either under Windows: unopkg list --shared test.txt test.txt would be a 0-byte file. Any ideas? ---rony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Windows' unopkg.exe does not differentiate between stderr and stdout, where does stdout go to when piping ?
On 2010-03-20 19:37, rony wrote: Hi Oliver, On 20.03.2010 17:29, Oliver Brinzing wrote: you can use: unopkg add myExtension.oxt--shared --verbose --log-file c:\mylog.txt but this won't log error's (http://qa.openoffice.org/issues/show_bug.cgi?id=79831), output is: ## Progress log entry 2010-03-20 16:54:33 ## Copying: myExtension.oxt Enabling:myExtension Enabling: Addons.xcu ... thank you very much for your hint! Wondering whether unopkg.exe under Windows is exhibiting erroneous behaviour (compared to its Linux behaviour) w.r.t. its output (cannot be redirected, nor piped). And as such whether it warrants a bug report. unopkg behaves rather strangely on Windows. There is no way to redirect its output in case of errors so you don't stand a chance of reporting an error back to a user - only that installation has failed. See also http://qa.openoffice.org/issues/show_bug.cgi?id=102854 Cheers -- Jan Holst Jensen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Windows' unopkg.exe does not differentiate between stderr and stdout, where does stdout go to when piping ?
Hi there, experimenting with OOo 3.2's unopkg.exe (under WindowsXP, SP3) it seems, that the output from unopkg.exe is only directed at stdout, whereas under Linux error messages (like given package not installed and the like) are directed to stderr, and normal messages to stdout. Is this intentional or a bug? Furthermore, trying to pipe normal output to grep seems to not work, i.e. something like: unopkg list --shared | grep CACHE would not work on Windows, but would under Linux (i.e. display the lines containing the string CACHE). (Yes, I made sure that the string is output as a result of running unopkg list --shared. The grep I am using on Windows is: GNU grep 2.5.3.) Actually, the following does not work either under Windows: unopkg list --shared test.txt test.txt would be a 0-byte file. Any ideas? ---rony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Windows' unopkg.exe does not differentiate between stderr and stdout, where does stdout go to when piping ?
Hi Rony, you can use: unopkg add myExtension.oxt--shared --verbose --log-file c:\mylog.txt but this won't log error's (http://qa.openoffice.org/issues/show_bug.cgi?id=79831), output is: ## Progress log entry 2010-03-20 16:54:33 ## Copying: myExtension.oxt Enabling:myExtension Enabling: Addons.xcu ... Oliver -- GnuPG key 0xCFD04A45: 8822 057F 4956 46D3 352C 1A06 4E2C AB40 CFD0 4A45 signature.asc Description: OpenPGP digital signature
