"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "releng/README" between
xorriso-1.5.2.tar.gz and xorriso-1.5.4.tar.gz

About: GNU xorriso creates, loads, manipulates and writes ISO 9660 filesystem images with Rock Ridge extensions. It is suitable for incremental data backup and for production of bootable ISO 9660 images. GNU xorriso is a statical compilation of the libraries libburn, libisofs, libisoburn, and libjte.

README  (xorriso-1.5.2):README  (xorriso-1.5.4)
------------------------------------------------------------------------------ ------------------------------------------------------------------------------
http:libburnia-project.org http:libburnia-project.org
------------------------------------------------------------------------------ ------------------------------------------------------------------------------
libisoburn/releng. By George Danchev <danchev@spnet.net> libisoburn/releng. By George Danchev <danchev@spnet.net>
and Thomas Schmitt <scdbackup@gmx.net> and Thomas Schmitt <scdbackup@gmx.net>
Test suite for xorriso and libburnia libraries. Test suite for xorriso and libburnia libraries.
Copyright (C) 2011 - 2012 George Danchev, Thomas Schmitt Copyright (C) 2011 - 2012 George Danchev
Copyright (C) 2011, 2012, 2019 Thomas Schmitt
Provided under GPL version 2 or later. Provided under GPL version 2 or later.
------------------------------------------------------------------------------ ------------------------------------------------------------------------------
The impatient tester will build libisoburn according to its README and then do The impatient tester will build libisoburn according to its README and then do
cd ./releng cd ./releng
./run_all_auto -x ../xorriso/xorriso ./run_all_auto -x ../xorriso/xorriso
More patient testers will first read the following description. More patient testers will first read the following description.
skipping to change at line 35 skipping to change at line 36
Directory ./releng of libisoburn contains a collection of test scripts and Directory ./releng of libisoburn contains a collection of test scripts and
auxiliary data. They exercise some typical use cases of building libisoburn auxiliary data. They exercise some typical use cases of building libisoburn
applications and running the ISO 9660 filesystem manipulation and CD/DVD/BD applications and running the ISO 9660 filesystem manipulation and CD/DVD/BD
burn program xorriso. burn program xorriso.
It is assumed that libburn and libisofs are installed, so that libisoburn It is assumed that libburn and libisofs are installed, so that libisoburn
can be configured and built. It is not mandatory that libisoburn is already can be configured and built. It is not mandatory that libisoburn is already
installed. The tests may use an installed xorriso program as well as a installed. The tests may use an installed xorriso program as well as a
freshly built one. freshly built one.
The test scripts explicitely demand /bin/bash as interpreter, although they The test scripts explicitly demand /bin/bash as interpreter, although they
would run on certain other shells too. If you get an error message like would run on certain other shells too. If you get an error message like
./run_all_auto: not found ./run_all_auto: not found
then consider to install /bin/bash. then consider to install /bin/bash.
If you decide against that, see below "Alternative Shells". If you decide against that, see below "Alternative Shells".
There are two groups of test scripts: There are two groups of test scripts:
auto_* gets started and watched by script run_all_auto. auto_* gets started and watched by script run_all_auto.
These tests have a moderate resource consumption and do These tests have a moderate resource consumption and do
not cause mechanical movements of drive trays. not cause mechanical movements of drive trays.
skipping to change at line 119 skipping to change at line 120
Data, which are possibly present on the media, get overwritten. Data, which are possibly present on the media, get overwritten.
The result gets check read and compared with the state of the input The result gets check read and compared with the state of the input
directory. MD5 mismatch causes a test failure. Differences to the directory directory. MD5 mismatch causes a test failure. Differences to the directory
state are reported but still regarded as success. state are reported but still regarded as success.
If a privilege command and optional arguments are given with --priv_cmd, If a privilege command and optional arguments are given with --priv_cmd,
then this command and arguments are used to launch the xorriso runs. then this command and arguments are used to launch the xorriso runs.
Command and arguments must be single words and be submitted altogether Command and arguments must be single words and be submitted altogether
as one single argument. On Solaris use: as one single argument. On Solaris use:
--priv_cmd pfexec --priv_cmd pfexec
./manual_isojigdo -x ../xorriso/xorriso ./manual_isojigdo -x ../xorriso/xorriso [-- [--md5 | --sha256]]
Exercises the production of a bootable Debian GNU/Linux image and its Jigdo Exercises the production of a bootable Debian GNU/Linux image and its Jigdo
files. This test downloads a Debian daily image for i386 of about 270 MB, files. This test downloads a Debian daily image for i386 of about 350 MB,
extracts its content and composes a new image. Thus it needs about 850 MB extracts its content and composes a new image. Thus it needs about 1100 MB
of disk space in releng/releng_generated_data when unpacked. Adding the daily of disk space in releng/releng_generated_data when unpacked. Adding the daily
image size itself, the total space used would peak at about 1.2 GB. image size itself, the total space used would peak at about 1.5 GB.
This test will only work with GNU xorriso or if libjte was installed already This test will only work with GNU xorriso or if libjte was installed already
when libisofs was built. Further it needs the program jigit-mkimage. Both when libisofs was built. Further it needs the program jigit-mkimage. Both
are part of package jigit, version >= 1.18, available at: are part of package jigit, version >= 1.22, available at:
http://www.einval.com/~steve/software/JTE/ http://www.einval.com/~steve/software/JTE/
Currently jigit builds only in GNU environments. Currently jigit builds only in GNU environments.
debian-cd currently uses the --md5 format. In future it will use --sha256.
Any auto_* script can be run on its own. Some of them demand option -x. Any auto_* script can be run on its own. Some of them demand option -x.
All general options are accepted. All general options are accepted.
./auto_cxx ./auto_cxx
Not included in GNU xorriso. Not included in GNU xorriso.
Exercises inclusion of xorriso/xorriso.h and libisoburn/libisoburn.h Exercises inclusion of xorriso/xorriso.h and libisoburn/libisoburn.h
in C++ programs and linking of the libraries. It might be necessary in C++ programs and linking of the libraries. It might be necessary
to set compiler options by shell variable CFLAGS before running the test. to set compiler options by shell variable CFLAGS before running the test.
It might be necessary to hand over the install directory of libburn and It might be necessary to hand over the install directory of libburn and
skipping to change at line 184 skipping to change at line 186
current $SHELL by running current $SHELL by running
./change_shell_to_use ./change_shell_to_use
which will modify the test scripts named run_all_auto , auto_* ,manual_*. which will modify the test scripts named run_all_auto , auto_* ,manual_*.
Known to be suitable are the following shells Known to be suitable are the following shells
GNU/Linux: /bin/bash GNU/Linux: /bin/bash
FreeBSD 8: /bin/sh FreeBSD 8: /bin/sh
Solaris: /bin/bash , /bin/i86/ksh93 Solaris: /bin/bash , /bin/i86/ksh93
In general, the shell should have Bourne shell ancestry. In general, the shell should have Bourne shell ancestry.
The script does not choose an interpreter explicitely and is safe to be run The script does not choose an interpreter explicitly and is safe to be run
inline: inline:
. ./change_shell_to_use . ./change_shell_to_use
One may set any interpreter path by running a sub shell and changing its One may set any interpreter path by running a sub shell and changing its
variable SHELL. E.g. by: variable SHELL. E.g. by:
( SHELL=/bin/my_shell" ; . ./change_shell_to_use ) ( SHELL=/bin/my_shell" ; . ./change_shell_to_use )
---------------------------------------------------------------------------- ----------------------------------------------------------------------------
Creating a new test script Creating a new test script
 End of changes. 8 change blocks. 
8 lines changed or deleted 10 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)