Skip to content
This repository has been archived by the owner on Oct 28, 2024. It is now read-only.

Local dependencies #10

Open
ivany4 opened this issue Jul 16, 2015 · 5 comments
Open

Local dependencies #10

ivany4 opened this issue Jul 16, 2015 · 5 comments

Comments

@ivany4
Copy link
Collaborator

ivany4 commented Jul 16, 2015

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.

@carlossless
Copy link
Owner

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.

@ivany4
Copy link
Collaborator Author

ivany4 commented Jul 16, 2015

Not if you wrap a bundle install into a script that installs it to a known location.

@carlossless
Copy link
Owner

Would that location be relative to tangerine? Or some system temp location?

@ivany4
Copy link
Collaborator Author

ivany4 commented Jul 16, 2015

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).

@ivany4
Copy link
Collaborator Author

ivany4 commented Jul 16, 2015

Or since you are using $BUILD_PATH for auxilary files, gems could easily go there.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants