Proof-of-concept dependency API.

[xaviershay]

Addresses #22

TODO/Questions:

• Why is SpecLite used instead of full Gem::Specification? Should we store both, or add required dependency data to SpecLite?
• Is Index the right spot for this?
• Tests.
• Documentation.

[copiousfreetime]

Why is SpecLite used instead of full Gem::Specification? Should we store both, or add required dependency data to SpecLite?

Its hard to remember exactly, since I wrote SpecLite more than 6 years ago :smile:. A couple of recollections I have are:

• keeping the api the same between the stickler client and the internal sticker repo management, i.e repo.delete(specification) works as the Client delete command and it passes it through to the server which then does repo.delete(specification) internally.
• I believe there are/were cases where I needed to pass a Specification to a rubygems class (which only needed it for name/version/platform) and I didn't have access to the full specification (or I didn't want to unpack the gem file to pull out the full specification).

Is Index the right spot for this?

Maybe. What I really what to have happen is stickler to implement the new index format and use that to drive the bundler api. new index repo

[copiousfreetime]

@xaviershay just checking to see if you need any more feedback from me.