95c9460c4a
Previously it was disciminated based on the entry mode. For directories, the inode was the offset of the corresponding goodbye tail mark while for all others it was the offset of the filename. By simply using the start offset as calculated from the corresponding goodbye table entry (which yields the archive offset of the filename), the code is simplified and the more ambiguous read_directory_entry() function can be used. The disatvantage of this approach is the need to keep track of the start and end offsets for each entry, as the end offset is needed in order to access the goodbye table of directory entries. The root node still has to be treated special, as it's inode is 1 as per fuse definition and it has no filename as per the pxar file format definition. Signed-off-by: Christian Ebner <c.ebner@proxmox.com> |
||
---|---|---|
.cargo | ||
debian | ||
docs | ||
etc | ||
qemu-io | ||
src | ||
tests | ||
www | ||
.gitignore | ||
Cargo.toml | ||
defines.mk | ||
Makefile | ||
README.rst | ||
rustfmt.toml | ||
TODO.rst |
``rustup`` Toolchain ==================== We normally want to build with the ``rustc`` Debian package. To do that you can set the following ``rustup`` configuration: # rustup toolchain link system /usr # rustup default system Versioning of proxmox helper crates =================================== To use current git master code of the proxmox* helper crates, add:: git = "ssh://gitolite3@proxdev.maurer-it.com/rust/proxmox" or:: path = "../proxmox/proxmox" to the proxmox dependency, and update the version to reflect the current, pre-release version number (e.g., "0.1.1-dev.1" instead of "0.1.0"). Local cargo config ================== This repository ships with a ``.cargo/config`` that replaces the crates.io registry with packaged crates located in ``/usr/share/cargo/registry``. A similar config is also applied building with dh_cargo. Cargo.lock needs to be deleted when switching between packaged crates and crates.io, since the checksums are not compatible. To reference new dependencies (or updated versions) that are not yet packaged, the dependency needs to point directly to a path or git source (e.g., see example for proxmox crate above).