cocoapods-podfile_patch 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 458241a69c9825a176500aa680c5f3529c1565f6
-  data.tar.gz: 39348fff4a039b73f68ab1edb75be9b9ccfdebf5
+  metadata.gz: db532f51a36d8ed122fe39dff75ad95af60c9ed4
+  data.tar.gz: 8801633e0db80778e6c28348a0e235b96458dcbc
 SHA512:
-  metadata.gz: 572effa83441d770ebe21c0596ae9f778d3f860744f2478addb3ea3480f808784d6c118174bdc5f23fdb6611528c27e72e769d09ed42d239456f34261bef279f
-  data.tar.gz: 5b5f96a44cfb9c67affb45c43e4a402ffaa489d2fb5d67b6a24501f2bde8a6dde90e593cf653aa4e19027b4a3fb8814e0ffcaca6e0cf4703e7d69074e2616b62
+  metadata.gz: 0d7bfa8726d98dfcb688ea598642082c60f85efc7e9e9f1c4cde0cc5aba2efe42283052f0965c868ff3dc85db8690f2d76d006ce9d3d6f0eb8a16de5562ef4c3
+  data.tar.gz: 303764e98bf05c41a6aea36a4b92e920b1119ca987e7e21902c9e92f0de991f0d542cbba2742354e089dfacf27e1eb8f282a5dfc9ed6a2e6a78a724a20a3fe65

data/README.md

@@ -1,35 +1,41 @@
 # cocoapods-podfile_patch
 
-This plugin provide the ability to override podfile in another file.
+This plugin provides the ability to override podfile in another file.
 
-Place a `Podfile.patch` at the same directory with Podfile. Configurate the pods
-in patchfile just like in Podfile. It will append to original podfile, and override
-the settings in podfile if duplicated.
+Place a `Podfile.patch` at the same directory with Podfile. Configure the pods in patchfile just like in Podfile. It will be merged to the original podfile, and override
+the pods settings in podfile if duplicated.
 
 For example:
 
 Podfile:
 ```
     use_patch_file!
-    target EVA do
+    target EVA-0 do
         pod "A", "1.5.3", :inhibit_warning => true
         pod "B", :path => "some/path"
     end
+
+    target EVA-1 do
+        pod "A", "1.5.3"
+    end
 ```
 
 Podfile.patch
 ```
-    target EVA do
+    target EVA-0 do
         pod "A", :path => "path/to/local/A"
     end
 ```
 
 The final result equal to 
 ```
-    target EVA do
+    target EVA-0 do
         pod "A", :path => "path/to/local/A"
         pod "B", :path => "some/path"
     end
+    target EVA-1 do
+        pod "A", :path => "path/to/local/A"
+    end
 ```
 
 This function is base on the parsed result of podfile. It means you could do ANYTHING
@@ -41,4 +47,38 @@ you do in podfile, i.e. your custom pod function or other plugins.
 
 ## Usage
 
-Just add `use_patch_file!` in podfile, and make your own `Podfile.patch`
+### Basic
+
+- add `use_patch_file!` in podfile
+- make your own `Podfile.patch` in the same directory with `Podfile`, and code just like in the podfile.
+- pod install 
+
+The most common case is to override a pod in podfile with a local pod. You could do like the example above. If you don't want to add a target, you also could do this:
+
+```
+pod "A", :path => "path/to/local/A"
+```
+
+Adding a pod in the root level of podfile is actually supported by the original podfile. It means add the pod to all targets. If you add a root level pod `A` in the patchfile, it will add `A` to all targets in podfile.
+
+
+### Advanced
+
+*How it works?*
+
+The patch file will be `eval` when `use_patch_file!` executed. That means you could do ANYTHING as in the podfile. The pod configuration in patchfile will be merged with podfile manually to resolve the conflicts.
+
+*Custom patchfile name*
+
+```
+use_patch_file! "your_custom_patchfile_name_or_path"
+```
+
+
+
+
+
+
+
+
+

data/lib/cocoapods-podfile_patch/gem_version.rb

@@ -1,3 +1,3 @@
 module CocoapodsPodfile_patch
-  VERSION = "0.1.0"
+  VERSION = "0.1.1"
 end

data/lib/cocoapods-podfile_patch/main.rb

@@ -0,0 +1,70 @@
+module Pod
+    class Podfile
+        module DSL
+            # Enable Podfile Patch feature.
+            # 
+            # Thid feature provide the ability to override podfile in another file.
+            #
+            # Place a `Podfile.patch` at the same directory with Podfile. Configurate the pods
+            # in patchfile just like in Podfile. It will append to original podfile, and override
+            # the settings in podfile if duplicated.
+            #
+            # For example:
+            #
+            # Podfile:
+            # ```
+            #     target EVA do
+            #         pod "A", "1.5.3", :inhibit_warning => true
+            #         pod "B", :path => "some/path"
+            #     end
+            # ```
+            #
+            # Podfile.patch
+            # ```
+            #     target EVA do
+            #         pod "A", :path => "path/to/local/A"
+            #     end
+            # ```
+            #
+            # The final result equal to 
+            # ```
+            #     target EVA do
+            #         pod "A", :path => "path/to/local/A"
+            #         pod "B", :path => "some/path"
+            #     end
+            # ```
+            #
+            # This function is base on the parsed result of podfile. It means you could do ANYTHING
+            # you do in podfile, i.e. your custom pod function or other plugins.
+            #
+            def use_patch_file!(patchfile_path = 'Podfile.patch')
+                
+                @current_patch_files ||= []
+                if @current_patch_files.include? patchfile_path
+                    # Yes, you could even use it recureively, but don't use the same patch file.
+                    raise "`use_patch_file!` called recursively. Most case is it's used in Patch file."
+                    return 
+                end
+                
+                @current_patch_files << patchfile_path
+                require 'cocoapods-podfile_patch/podfile_patch'
+                @patch_target = PodfilePatch.new.load_patch_target self, patchfile_path
+                @current_patch_files.delete(patchfile_path)
+            end
+
+        end
+    end
+end
+
+module Pod
+    class Podfile
+        old_initialize_function = instance_method(:initialize)
+        define_method(:initialize) do |defined_in_file = nil, internal_hash = {}, &block|
+            old_initialize_function.bind(self).(defined_in_file, internal_hash, &block)
+
+            if not @patch_target.nil?
+                PodfilePatch.new.merge_patch_and_original_podfile(self, @patch_target)
+            end
+        end
+    end
+end

data/lib/cocoapods_plugin.rb

@@ -1,70 +1 @@
-module Pod
-    class Podfile
-        module DSL
-            # Enable Podfile Patch feature.
-            # 
-            # Thid feature provide the ability to override podfile in another file.
-            #
-            # Place a `Podfile.patch` at the same directory with Podfile. Configurate the pods
-            # in patchfile just like in Podfile. It will append to original podfile, and override
-            # the settings in podfile if duplicated.
-            #
-            # For example:
-            #
-            # Podfile:
-            # ```
-            #     target EVA do
-            #         pod "A", "1.5.3", :inhibit_warning => true
-            #         pod "B", :path => "some/path"
-            #     end
-            # ```
-            #
-            # Podfile.patch
-            # ```
-            #     target EVA do
-            #         pod "A", :path => "path/to/local/A"
-            #     end
-            # ```
-            #
-            # The final result equal to 
-            # ```
-            #     target EVA do
-            #         pod "A", :path => "path/to/local/A"
-            #         pod "B", :path => "some/path"
-            #     end
-            # ```
-            #
-            # This function is base on the parsed result of podfile. It means you could do ANYTHING
-            # you do in podfile, i.e. your custom pod function or other plugins.
-            #
-            def use_patch_file!(patchfile_path = 'Podfile.patch')
-                
-                @current_patch_files ||= []
-                if @current_patch_files.include? patchfile_path
-                    # Yes, you could even use it recureively, but don't use the same patch file.
-                    raise "`use_patch_file!` called recursively. Most case is it's used in Patch file."
-                    return 
-                end
-                
-                @current_patch_files << patchfile_path
-                require 'cocoapods-podfile_patch/podfile_patch'
-                @patch_target = PodfilePatch.new.load_patch_target self, patchfile_path
-                @current_patch_files.delete(patchfile_path)
-            end
-
-        end
-    end
-end
-
-module Pod
-    class Podfile
-        old_initialize_function = instance_method(:initialize)
-        define_method(:initialize) do |defined_in_file = nil, internal_hash = {}, &block|
-            old_initialize_function.bind(self).(defined_in_file, internal_hash, &block)
-
-            if not @patch_target.nil?
-                PodfilePatch.new.merge_patch_and_original_podfile(self, @patch_target)
-            end
-        end
-    end
-end
+require 'cocoapods-podfile_patch/main'

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: cocoapods-podfile_patch
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Gao
@@ -53,6 +53,7 @@ files:
 - cocoapods-podfile_patch.gemspec
 - lib/cocoapods-podfile_patch.rb
 - lib/cocoapods-podfile_patch/gem_version.rb
+- lib/cocoapods-podfile_patch/main.rb
 - lib/cocoapods-podfile_patch/podfile_patch.rb
 - lib/cocoapods_plugin.rb
 - spec/command/podfile_patch_spec.rb