squashfs-tools-ng.git/bin, branch fixes-1.2.0

rdsquashfs: improve unpacking error message on Windows

2022-12-14T14:14:18+00:00

Print a proper error description instead of just an error code. If the error is ERROR_FILE_EXISTS, print out a hint that this might be caused by a case in-sensitivity issue. Signed-off-by: David Oberhollenzer

Move gensquashfs specific code from libfstree to gensquashfs

2022-11-22T13:45:32+00:00

The "from dir" and from "from file" code, as well as the "sort file" code is specific to gensquashfs, so move them there and the test cases as well. The medium term idea is to reduce libfstree to a stub, merge it into the generic writer and ultimately hoist that into libsquashfs. Signed-off-by: David Oberhollenzer

filemap xattr: slightly improve error reporting

2022-11-21T14:27:09+00:00

- When printing an error, specify the filename and line number - Always print an error, including out of memory conditions - Fail if we encounter a line that we don't recognize Signed-off-by: David Oberhollenzer

filemap xattr: use sqfs_u8 data type for xattr value blobs

2022-11-21T14:25:53+00:00

The xattr values are not strings, they are arbitrary byte blobs. To be on the safe side tough, we should still allocate the space for the extra null byte and propperly initialize the buffer. Signed-off-by: David Oberhollenzer

gensquashfs: Add example for the xattr filemap to the help text

2022-11-19T19:09:12+00:00

Signed-off-by: David Oberhollenzer

gensquashfs: split the help text up into smaller parts

2022-11-19T18:24:38+00:00

It's just too darn big, crossing the maximum guaranteed by C99. Signed-off-by: David Oberhollenzer

gensquashfs: simplfy the help text a bit

2022-11-19T17:23:28+00:00

The help text should provide a short, concise explanation, for quickly lookup up how to use the programs. For the input formats, this is mostly covered by the examples themselves. The detailed description can remain in the man page. Signed-off-by: David Oberhollenzer

Add a man-page section about the xattr file format

2022-11-19T15:59:41+00:00

Signed-off-by: David Oberhollenzer

filemap xattr: use file istream from libio instead of stdio FILE

2022-11-18T15:21:12+00:00

The line-by-line reading function in the io library was specifically added for this kind of use case, so we don't have to handle trimming of lines, don't have to touch getline() and it's convoluted error handling (return value -1 could mean either EOF or error). The code that searches for '\n' and replaces it with '\0' can be removed as well and a memory leak involving "line" is removed along the way. Signed-off-by: David Oberhollenzer

filemap xattr: simplify error handling, freeing

2022-11-18T15:21:12+00:00

- Some of the error/cleanup paths are merged. - Struct fields don't have to be set to NULL if the entire struct is free'd immediately after. Signed-off-by: David Oberhollenzer