Changing an imported library using cocoapods

Question

I am working on a project using cocoapods and suddenly I see myself doing some changes in one of the libraries. How can I ensure that those changes will never be override by a <

Answer 1

Just want to add my few cent to the answer. I encounter the same problem. As someone suggested above too I went to subclass-ing the pod lib. I was using ACEDrawingView and it has property image which is readonly. I subclass-ed it and made this property read/write. I personal feel going by sub-class is more elegant and hassle free solution to this kind of problem. Unless there is huge development you want to do on side of your main project.

Answer 2

@pgb and wattson provided me good information but ultimately the problem was in a combination of things.

I don't know why but it seems that cocoapods 0.22 handles headers differently. I uninstalled cocoapods and installed the version 0.20.2.

To check the version of cocoapods I have used gem query and I have removed the cocoapods with gem uninstall cocoapods and installed the cocoapods with gem install cocoapods --version 0.20.2.

I have used my podfile like this:

'WhirlyGlobe', :podspec => 'https://raw.github.com/tiagoalmeida/WhirlyGlobe/master/WhirlyGlobe.podspec'

Where podspec points to my new podspec. I made like this because I need to remove the :tag from the original podfile (otherwise it always points to the same spot) and this way I have more control over the file.

In the podspec I have changed the source:

s.source = { :git => "https://github.com/tiagoalmeida/WhirlyGlobe.git"} 

To point into my fork and removed the tag.

Thanks @pgb and @wattson for the attempts to help me. Upvoted both because they were both usefull.

Answer 3

There is an another way exist where you can fork the repository , modify the changes and maintain the library through cocoapods for future bug fixes and feature enhancement .....

I have recently published tutorial for the same here https://medium.com/@mihirpmehta/how-to-modify-cocoapods-library-within-pods-647d2bf7e1cb

Answer 4

You can fork a repository and then add your forked repo as a pod, so say you've forked the repo to https://github.com/tiago/ThePodProject.git, then set the pod to:

pod 'ThePodProject', :git => 'https://github.com/tiago/ThePodProject.git'

see here for more detail (under "From a podspec in the root of a library repo")

Answer 5

You are close to having it working with your forked repository.

I just tried it with the following Podfile:

pod 'WhirlyGlobe', :git => 'https://github.com/tiagoalmeida/WhirlyGlobe'

It downloaded WhirlyGlobe and then failed because hg was missing. I simply installed it using Homebrew: brew install mercurial and then runnning pod install was able to install all the dependencies.

The project compiles, but I'm not sure it works, go ahead and try it.

Be aware that it took a really long time to download and compile all the dependencies (shapelib in particular).

Answer 6

Saving custom changes using only Git (no forking)

For those looking for a simple solution, I have successfully solved this problem by using git stashes.

As mentioned, pod update will overwrite any changes you made. However, if you're using git what I like to do is commit all my changes except for my pod changes.

Once the only changes I have on my branch are the Pods changes, I stash those changes by running git stash save "Custom Cocoapod changes, apply after every pod update". You can give it any message you'd like by changing the text between the "".

This command has the side effect of reseting your working directory to the previous HEAD, so if you want to reapply those stashes you can just run git stash apply to get those changes back in, and then you can commit them to save them.

Don't use git stash pop as this will delete the stash after applying it.

Now, at some undetermined time in the future, when you update your pods and its time to apply the stash again, what you're going to want to do is run git stash list. this will return a list of all the stashes you've made with the most recent being zero indexed. You'll probably see something like this:

stash@{0}: On featureFooBar: foo bar
stash@{1}: On Master: Custom Cocoapod changes, apply after every pod update
...

If the custom cocoa pods changes stash is in stash@{0} then perfect, you can just run a git stash apply again and you'll get those changes on your working directory. Otherwise once you find which stash number your pods changes are you can apply that stash by running git stash apply stash@{1}

Applying stashes is easiest when you have a clean working directory on the same branch but thats not required. This page gives a good description of git stash and how to use it otherwise.

This is not the most full proof solution since I can foresee some issues when you have multiple people on the same project, but it's a simple way to solve this without resorting to more involved solutions.