Didn't notice it because vendor/ was already populated on my dev
machine, but did notice it in Docker build.
Docker build now consumes devsetup like regular user, so this should
catch future problems.
Remove remaining curl|shit functionality from lazy.sh (no checkout logic
needed anymore).
refs #35
sphinx-versioning only build branches / commits with a 'docs/conf.py',
otherwise:
=> Gathering info about the remote git repository...
=> Getting list of all remote branches/tags...
=> Found: docs_theme master resumable_send_recv 0.0.1 0.0.2
=> With docs: 0.0.2
=> Root ref master not found in: 0.0.2
refs #35
Abandons stderr special-casing:
* looks weird on shell and IO redirection to same file because of
interleaving of stdout and stderr
* better than a separate dedicated outlet because it does not require
additional configuration
fixes#28
BREAK SEMANTICS CONFIG
* Idempotent clone_and_build.sh does everything
* Add documentation for how to build in Docker
Had to sacrificy go generate because stringer apparently can't handle
vendor directory used by go dep, fails with error
on go generate rpc/frame_layer.go
refs #37
In contrast to any 'something<' mapping, a '<' mapping cannot be unique
Thus, '<' mappings are thus just an append to target, which is exactly
what we get when trimming empty prefix ''.
Otherwise, given mapping
{ "<": "storage/backups/app-srv" }
Before (clearly a conflict)
zroot => storage/backups/app-srv
storage => storage/backups/app-srv
After:
zroot => storage/backups/app-srv/zroot
storage => storage/backups/app-srv/storage
However, mapping directly with subtree wildcard is still possible, just
not with the root wildcard
{
"<" "storage/backups/app-srv"
"zroot/var/db<": "storage/db_replication/app-srv"
}
fixes#22
While filesystems is also not the right term (since it excludes ZVOLs),
we want to stay consistent with comments & terminology used in docs.
BREAK CONFIG
fixes#17
