Skip to content

Dependency Isolation

trans edited this page Jan 1, 2013 · 3 revisions

Dependency Isolation

NOTE YET IMPLEMENTED

Developers often need to isolate a project's dependencies, both to ensure best-fit version resolution and to isolate the project from any malformed libraries that might erroneously clobber lib paths of another project (yes, sadly this can happen). Library makes this easy to handle in either of two ways.

First you can set the run mode to "development".

    export RUBY_LIBRARY_MODE="development"

This mode will have Library look for a .index file in a Project's root directory relative to the current working directory. If will use the requirements information of this file to peardown the current library ledger to just the needed libraries with the best-fit of versions for all dependencies involved. Note, this will not automatically download missing dependencies or best-fit versions from a remote source (e.g. rubygems.org). So you will still have to install potential dependencies first.

The other option is to generate an isolation file. MORE TO COME...