Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Private pods - best practices

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers.

Private pods - best practices

A pretty opinionated talk for CocoaPods state of the union (WWDC) event.

The talk is a result of some practices applied after dealing with private pods in a bigger team for quite awhile. Opinions are my own and you shouldn't take them as facts.

Avatar for Marin Usalj

Marin Usalj

June 09, 2014
Tweet

More Decks by Marin Usalj

Other Decks in Programming

Transcript

  1. WHY

  2. NO PRIVATE SPEC SERVER USE :GIT pod 'SiliconKit', :git =>

    'pods.local/siliconkit.git' OPTIONALLY, USE :TAGS pod 'SiliconKit', :git => '...', :tag => '1.0.3'
  3. !"" Source # !"" Data # !"" Investors # !""

    Networking # # !"" Authentication # # !"" Companies # # !"" Investitions # $"" Presenters
  4. EXCLUSIVE PODSPECS s.subspec 'ARC' do |arc| arc.source_files = 'SiliconKit/**/*.{h,m}' arc.requires_arc

    = true end s.test_spec do |test| test.source_files = 'SiliconKitTests/**/*.{h,m}' test.framework = 'XCTest' test.dependency 'Kiwi/ARC' test.dependency 'Kiwi/NonARC' end