iOS: updating dependencies

Richard Newman rnewman at mozilla.com
Tue Sep 1 22:29:36 UTC 2015


Three errors that I've noticed today. Pay heed!

1. You have an entry in Cartfile like this:

  github "foo/bar"

You commit a change to github.com/foo/bar. You do not tag a release, but
there are previous tagged releases.

Carthage will check out the last tagged release, ignoring your fixed commit!

The fix: either tag a new release, or change that line to:

  github "foo/bar" "somebranch"

I have added comments to our Cartfile:

  github "foo/bar"        # Implicit: latest tag.


2. You update a dependency, but you either (a) don't run a checkout, or (b)
don't commit your changes to Cartfile.resolved, or (c) have a local
Carthage checkout that disagrees with the Cartfile that you committed.
Others will see build failures, but your build is working fine!


3. You have a dependency on a branch where the commit referenced in
Cartfile.resolved has disappeared due to an upstream rebase. This just
happened to us. Someone needs to run ./update.sh and commit the resolved
result.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/mobile-firefox-dev/attachments/20150901/55037593/attachment.html>


More information about the mobile-firefox-dev mailing list