[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: xorriso version in error stream
From: |
Thomas Schmitt |
Subject: |
Re: xorriso version in error stream |
Date: |
Mon, 22 Apr 2024 17:40:40 +0200 |
Hi,
Hagspiel, Michael wrote:
> Why is the version string written to the error stream?
Because in many use cases stdout is used for the resulting ISO image
or for information texts which shall be parsed by other software.
> And is there any possibility to prohibit this output on the error stream?
No.
Some ideas:
You may wrap the xorriso run in a run of a program which drops the first
line on stderr.
Or you may get a GNU xorriso tarball like
https://www.gnu.org/software/xorriso/xorriso-1.5.6.pl02.tar.gz
to remove in xorriso-1.5.6/xorriso/xorriso_main.c the unconditional call:
/* Put out program name and version to stderr only if not done already now */
yell_xorriso();
and/or to change the fprintf()-call in yell_xorriso():
static void yell_xorriso()
{
fprintf(stderr,
"%sxorriso %d.%d.%d%s : RockRidge filesystem manipulator, libburnia
project.\n\n",
...
before compiling it, according to xorriso-1.5.6/README.
Said this:
Automated users of xorriso should rather check the exit value of the
program run. The command -return_with can be used to set a severity
threshold for the exit value to become non-zero even if the program
run did not abort prematurely (which is governed by command -abort_on).
Have a nice day :)
Thomas