Similar to #108, the internal helper method for appending long links is only accessible through APIs that attempt to access the filesystem.
It would be great if it were possible to pass a header (with symlink or hardlink entry_type) and a name + link_name as Path and have the builder insert the necessary long-name headers. I.e. an equivalent to append_data
Maybe some general intermediate-level API is missing for adding headers and data separately to orthogonalize the construction of complicated headers that must be written in several parts (long name, long links, sparse header) and their associated data chunks. A single function taking several enums to cover all those combinations might work too.
Similar to #108, the internal helper method for appending long links is only accessible through APIs that attempt to access the filesystem.
It would be great if it were possible to pass a header (with symlink or hardlink
entry_type) and aname+link_nameasPathand have the builder insert the necessary long-name headers. I.e. an equivalent toappend_dataMaybe some general intermediate-level API is missing for adding headers and data separately to orthogonalize the construction of complicated headers that must be written in several parts (long name, long links, sparse header) and their associated data chunks. A single function taking several enums to cover all those combinations might work too.