I was expecting to also see pbxproj updates in this PR - otherwise the demo project will fail to build on new instdalls (Because its trying to reference the old libsvgkit-2.0.0 file)?

@adamgit This is the prepare before we release v2.1.0. Please have a check.

It seems the Demo project using the SVGKit.framework. That static library is a standalone build configuration and not related to Demo project...But anyway, I can update it.

@adamgit Any reason we generate the static library with that version number ? Why not just SVGKit-iOS.a ? I've joined other open source organization. The static library like SDWebImage or CocoaLumberjack does not append this version number.

I am not sure, but ... I think it's a standard that Apple/Xcode used?

I agree that if we could get safely remove the version from the name then it would make the library easier for us to maintain!

I agree that if we could get safely remove the version from the name then it would make the library easier for us to maintain!

This filed is safe. The number is just appended to file name...(This does not compiled to static library binary), but people who build static library by theirself, already know what the version is. So it's no need to add it at all (And cause we manual change that number each time release). I think we can just remove that. (actually this does not cause any issue....file name :))

See the static library from SDWebImage && CocoaLumberjack

@adamgit Hi. Good news. It seems that after I sending the email to claim the owner of SVGKit from CocoaPods forum. They add you and me to the CocoaPods trunk owner.

➜ pod trunk info SVGKit

SVGKit
    - Versions:
      - 0.0.1 (2014-05-19 21:43:42 UTC)
      - 1.0 (2014-05-19 21:49:54 UTC)
      - 1.2.0 (2014-07-01 11:48:47 UTC)
    - Owners:
      - Mirko Olsiewicz <mirko.olsiewicz@olsiewicz.de>
      - adam <adam.m.s.martin+cocoapods@gmail.com>
      - Alexandros Salazar <asalazar@weather.com>
      - DreamPiggy <lizhuoli1126@126.com>

Now we can upload the podspec into the trunk. So that all CocoaPods user can use a release version instead of current branch dependency like pod 'SVGKit', :branch => '2.x'

So I'm waiting for your release of SVGKit 2.1.0. After you push a new git tag 2.1.0 (Don't append something like v2.1.0. because CocoaPods && Carthage use the git tag for version number). I can upload the Podspec to the CocoaPods for release.

@adamgit I upload the 2.0.0 version podspec to the CocoaPod Trunk. CocoaPods user can now use the 2.0.0 tag release in their podfile. https://cocoapods.org/pods/SVGKit

And, is there any pending PR to merge for 2.1.0 release ? Maybe we can start a git tag release. The 2.0.0 can works for Xcode 10 now, but it still seems far away from the current 2.x branch lastest commit.

Both CocoaPods or Carthage, by default use the git tag for the raw version number.
If you tag a git tag use v2.1.0, people using the semversion will cause issue.

CocoaPods

pod 'SVGKit', '~> v2.1.0' # This will not work.
pod 'SVGKit', '~> 2.1.0' # This works

Carthage

github 'SVGKit/SVGKit', ~> 2.1.0