1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
[]
= "ferrosys-cli"
= "Command-line ext2/3/4 formatter, inspector, and extractor built on ferrosys"
= true
= true
= true
= true
= true
= true
= ["ext4", "filesystem", "mkfs", "disk-image", "cli"]
= ["command-line-utilities", "filesystem"]
# The package's front page on a registry.
= "README.md"
# The guide, not docs.rs: the only target here is a binary with `doc = false`, so a
# rustdoc site for this package would be an empty page.
= "https://gregordinary.github.io/ferrosys/cli.html"
# The binary is `ferrosys`; the package it ships in is `ferrosys-cli`.
# `doc = false`: the binary shares the name of the `ferrosys` library, and rustdoc would
# otherwise write both to the same `target/doc/ferrosys` path. The command line is
# documented in the guide, not in rustdoc.
[[]]
= "ferrosys"
= "src/main.rs"
= false
[]
# The filesystem itself. The `tar` feature carries the archive source `format --from-tar`
# reads, and `dir` the directory walk behind `format --from-dir`. The integration gates
# build filesystems the archive source cannot describe (a socket) and read them back, so
# they drive the library directly as well as the binary; an integration test links a
# normal dependency, so this one entry serves both.
= { = true, = ["tar", "dir"] }
# Typed error enums. Build-time proc-macro only; no runtime footprint. Argument
# parsing is hand-written and takes no dependency.
= { = true }
[]
# Scratch images and archives for the integration gates; never shipped.
= { = true }
# Building the tar archives the round-trip gates feed back in, and reading back the ones
# `extract --to-tar` writes. The binary itself needs no tar crate: it writes archives
# through the library's archive sink, which takes a plain writer.
= { = true }