Skip to content
nkpart edited this page Apr 28, 2011 · 3 revisions

Version 0.7

clearer .kit directory structure

This release involves a major shake up of the .kit directory where local packages are stored and extracted from. In older versions, compressed bundles were kept in ~/.kit/repository/kits/$NAME/$VERSION. The new release expects them to be found in ~/.kit/cache/local/$NAME/$VERSION. This is prep for a world where kits might come from other places, and stored in ~/.kit/cache/<repository>.

Kit will warn you if you have packages under the old structure, with instructions on how to move them to the new folder.

tidier package referencing

In older versions of kit, kits were extracted into the Kits sub-directory of your project. If multiple projects depended on the same kits, you end up with multiple exploded copies (project-a/Kits/dep-0.1 and project-b/Kits/dep-01).

0.7 cleans this up, by extracting every kit just once into ~/.kit/packages/$NAME-$VERSION. The KitDeps.xcodeproj then references content from this directory via absolute paths.

The Kits sub-directory is now much cleaner, containing just the generated files that are specific to a project.

dev-packages [experimental]

I'm throwing this feature out for comment at the moment, as it's something I think will be really useful, but could be solved in other ways.

The use-case for this feature is that you have a project that you wish to modify/develop in the context of a parent project. Currently, you have to do a lot of publish-local/update calls every time you make a change to the dependency and wish to test it in the parent. dev-packages makes this easier.

If you have a dev-packages sub-directory in your project, kit will look for packages in that folder before looking in the ~/.kit cache. The packages are searched for by name only, without a version tag on the folder.

Eg. Given the following project structure:

KitSpec
MyProj.xcodeproj/*
Classes/*
dev-packages/
    flurry-analytics/
        src/
        KitSpec
        etc.

No matter what version of flurry-analytics that the top-level KitSpec specifies, kit will reference source from dev-packages/flurry-analytics.

Clone this wiki locally