This bootstraps the client with the `draft pack-repo` plugin, then installs or updates the packs using that plugin. This removes the existing functionality on how packs are written to ~/.draft/packs, but the workflow is identical to the end-user.
This replaces the hard-coded built-in packs with a generator that uses
go-bindata to read the `packs/` directory and generate an internal
representation that is compiled into the binary.
It adds the make target `generate`, which is called by the build and
cross-compile steps.
Doing things this way has the following advantages:
- Managing built-in packs is much easier (see #95)
- The packed binaries are compressed, so overall memory footprint is
smaller
The main disadvantage is that it is harder to share files across the
packs. However, it is likely that these paks would diverge over time
anyway.
Matthew Fisher
Simon Bennett
Matt Butcher