Chris

Setting the location and path shouldn't be the library consumer's responsibility; it should be the library's. Imo there should simply be a flag on the schema that enables spec-compliant errors....

This is kind of a big deal imo. I would call spec violations like this a deal-breaker for any API that hopes to see widespread use.

Related: #110

It also makes sense to allow negation: ``` libraries: hiredis: repository: [email protected]:redis/hiredis.git commit: v0.13.2 project: ensures: - lib/libhiredis.a - !lib/libhiredis.dylib ``` And in those cases, maybe Needy should just delete...

We definitely want the directory cache to be cleared aggressively if disk space is low.

Before we expand this any further, I want to revise what we currently have. If possible I want to simplify things a lot to make things more maintainable. The requirement...

I also need to make this caching much more transparent. I want it to be something that everyone can benefit from. Not just a massive chunk of code with narrow...

#144 simplifies things a lot without compromising features. Now I'm much more comfortable expanding on this.

Agreed. One thing in particular: Testing the various runtime / api level combinations would be a really good thing.

Sounds good. I think I would prefer the subcommand style syntax over the flag style (`needy config set platforms.android.api-level 17` over `needy config --set platforms.android.api-level 17`). It's a bit closer...