Skip to content

Conversation

@segiddins
Copy link
Member

If the only dependencies for a specification name are optional, that specification will not be activated. If there is a strong dependency as well, than the requirements imposed by optional dependencies will be taken into account.

\c @indirect

@alloy you might find this interesting

@segiddins segiddins force-pushed the seg-optional-dependencies branch from 0e9fa20 to f510630 Compare July 30, 2016 20:41
@alloy
Copy link
Member

alloy commented Jul 30, 2016

Very neat 👌

Just out of curiosity; what client, if any, is going to be using this?

@segiddins
Copy link
Member Author

@alloy I want to add this to bundler & rubygems and maybe even CocoaPods

@indirect
Copy link

I am 👍 on this, great groundwork for us to hopefully add optional deps in RubyGems 3.1 or something like that.

@segiddins segiddins force-pushed the seg-optional-dependencies branch from b194d0b to 40eecc7 Compare November 30, 2016 22:56
@segiddins
Copy link
Member Author

Rebased

@segiddins segiddins force-pushed the seg-optional-dependencies branch from 40eecc7 to 9b7162b Compare January 5, 2017 21:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants