-
Notifications
You must be signed in to change notification settings - Fork 3
Local dependencies #10
Comments
Currently the bootstrapping process only checks for it's dependencies, but doesn't take any action if the dependencies are missing. So in short it's up to the user to actually install missing dependencies. Also, if we were to add automatic dep resolution, all of the internals that use these dependencies would have to know where the local executables are stored and run them instead than the global ones. |
Not if you wrap a bundle install into a script that installs it to a known location. |
Would that location be relative to tangerine? Or some system temp location? |
I would say relative. So that if you have two apps with tangerine they do not try to write to the same location. (They might have different versions of tangerine with different dependencies). |
Or since you are using $BUILD_PATH for auxilary files, gems could easily go there. |
I think it would be better to get the dependencies locally so that it does not conflict with other gems on the system. So, just adding a Gemfile with cupertino and xcpretty dependencies that would install locally rather than system-wide.
The text was updated successfully, but these errors were encountered: