This is a seven-part series to extract librad modules into top-level crates in
order to improve modularity. The following approach is followed:
crates are still re-exported through librad, preserving the module hierarchy
where possible / sensible
the module hierarchy in the test crates is left untouched, ie. all tests
happen through librad
the move is motivated by allowing the v3 replication to live in it's own crate
(and thus be able to pick smaller dependencies). We don't go beyond that for
now, namely the big librad module hierarchies net and git are left
intact. This is because splitting them would cause even more churn, and it is
not immediately obvious how to best split them.
to avoid naming conflicts, protocol related crates are prefixed with link-
(incl. their directories), while crates which could also be released
standalone don't have a prefix. No attempt is made in this series to adjust
the names of already existing crates, although that might be submitted shortly
after
This is a seven-part series to extract
libradmodules into top-level crates in order to improve modularity. The following approach is followed:librad, preserving the module hierarchy where possible / sensibletestcrates is left untouched, ie. all tests happen throughlibradlibradmodule hierarchiesnetandgitare left intact. This is because splitting them would cause even more churn, and it is not immediately obvious how to best split them.link-(incl. their directories), while crates which could also be released standalone don't have a prefix. No attempt is made in this series to adjust the names of already existing crates, although that might be submitted shortly after