Source directories and packages (toplevel)
------------------------------------------
-Note that unlike everything else, these keys `packages` and `subdirs`
-are read only from `Cargo.nail` (see "Limitations and bugs", below).
+Note that unlike everything else, these keys (`packages` and
+`subdirs`) are read only from `Cargo.nail` (see "Limitations and
+bugs", below).
These keys specify a combination of (i) a mapping from package name to
source subdirectory (ii) a set of subdirectories whose `Cargo.toml`
* `subdirs`: a list of subdirectory names to process.
- Each subdirectory's `Cargo.toml` will be massaged; also, the
- subdirectory will be examined to see what package it contains and
- it will be used as the source for that package, unless that
+ Each subdirectory's `Cargo.toml` will be massaged. Also, the
+ subdirectory will be examined to see what package it contains; it
+ will then be used as the source for that package, unless that
package appears in an entry in `packages`, or an earlier entry in
`subdirs`.
['myproject','mylibrary']`). Or it can be single multi-line
string containing one subdirectory name per line; in that
case, `#`-comments are supported and tabs and spaces are ignored
- (See "Most basic example usage" above.)
+ (see "Most basic example usage" above.)
In each case the subdirectory should usually be a relative pathname;
it is relative to the directory containing `Cargo.nail`.