-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DSL directive to exclude subspecs in the Podfile #40
Comments
I’m of the opinion that we should leave this open for now and see if others have similar needs. |
I think the exclude method would be very useful. I need this functionality too. |
This has been considered a desirable feature but we are holding off because it the additional complexity is worth it. |
Blocked by #81 |
Agreed. |
As an aside, remember that you can still use Ruby in your Podfile. E.g. %w{ ADT Annotation BlockMethod }.each do |subspec|
pod "libextobjc/EXT#{subspec}"
end |
The directive should allow to exclude any dependency. This more general solution is useful in case you might want to install a fork: pod 'libA', :exclude => 'depB'
pod 'depBFork' Also I'm starting to wonder wether the DSL should support a block for the pod 'libA', '> 1.0' do
exclude 'depB'
git 'example.com'
head!
end |
I'm not fond of the |
Almost none of the attributes specified here are actions, they are a specification/configuration. The |
Good point… Well I'm probably used to see But still, |
Moving to #150 |
I have recently added an easy approach solution for those who are wondering what to do in a locked condition that exclusion of pod dependency is absolutely a must. |
I shouldn't have to write the following (well, regex it from the lockfile) in order to exclude a single subspec which has a broken dependency:
The text was updated successfully, but these errors were encountered: