[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libcdio-devel] Ready for testing: libcdio branch trackno-higher-one

From: Thomas Schmitt
Subject: Re: [Libcdio-devel] Ready for testing: libcdio branch trackno-higher-one with .cue files
Date: Sun, 30 Dec 2018 16:35:27 +0100


> Edd also has a test proposed for
> libcdio_paranoia that he has indicated he would like to propose that you
> can use.

I guess you mean

The BIN/CUE tests in libcdio-paranoia look quite different from those
in libcdio. For example, no .right file but rather an awk program is
used to check the output.

Hopping along the file list of the changeset:
I need not change because i need no awk and make no new script.
No need for me to expand .gitignore because my three new files shall go to git.
In test/ i need to register my new .right file rather than Edd's
new script.
Edd does not need to expand test/data/ because his data get


This all depends on my two commits to libcdio branch "trackno-higher-one".
In principle they are ready for merging.

But in detail there is still the question of log message level:

In order to see the error messages caused by my intentionally wrong .cue
files i had to use cdio_warn() rather than cdio_log(log_level,) as used
for all other error messages in parse_cuefile().

Shall i keep cdio_warn() or shall i change them to cdio_log(log_level,) ?

Have a nice day :)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]