Story: Use ipfs-pack to Track Directory Structure & Contents

[flyingzumwalt]

This is part of #95 Epic: Register a Directory and Serve it on IPFS.

For technical details see the draft proposal for ipfs-pack

@jbenet says

think of ipfs-pack like this: "save the output of ipfs add --only-hash such that we can "make absolutely damn sure" what this archive (pack) contains later, that it hashes to the exact same values, and that we move it around safely".

Excerpt from ipfs-pack draft proposal:

ipfs-pack db creates (or updates) a temporary ipfs object database
This command creates (or updates) a temporary ipfs object database (eg at .ipfs-pack/db). This object database contains positonal metadata for all IPLD objects contained in the pack. (It follows the ipfs repo filestore metadata concerns). It MAY be a different, simpler object-db format, or be a full-fledged ipfs node repo using filestore.

Sub-Stories

• Story: [ipfs-pack] Create or Update a pack manifest file #96 Create a pack manifest file
• Create or Update a Local Pack Object Repository #131 Create or Update a Local Pack Object Repository
• Story: [ipfs-pack] Validate a directory against a manifest file #97 Validate a directory against a manifest file

[flyingzumwalt]

#131 isn't explicitly covered, but ipfs-pack make builds the repo for you. Considering that sufficient to close this issue.