Breaking: Removing old Lumberjack
Installing CocoaLumberjack via git read-tree, up to commit tagged 2.0.0-beta4. Specifically, I did these steps:

- git remote add CocoaLumberjack_remote https://github.com/CocoaLumberjack/CocoaLumberjack.git
- git fetch CocoaLumberjack_remote
- git checkout -b CocoaLumberjack CocoaLumberjack_remote/master
- <switch back to branch master or whatever one I’m working on>
- git read-tree --prefix=Source/Vendor/CocoaLumberjack/Classes -u 2.0.0-beta4:Classes

Is this a long-term solution? From my perspective, no. This is an initial step to getting CL 2.x support without changing too much of the directory structure. In the future I want to look into moving the SVGKit project into a separate 'Framework' Folder, and the demos into a separate folder, and just have those builds have respective podfiles for building.
Installing CocoaLumberjack (Framework) via git read-tree, up to commit tagged 2.0.0-beta4, because the framework builds are split depending on platform (OS X vs. ios) Specifically, I did these steps:

- git remote add CocoaLumberjack_remote https://github.com/CocoaLumberjack/CocoaLumberjack.git
- git fetch CocoaLumberjack_remote
- git checkout -b CocoaLumberjack CocoaLumberjack_remote/master
- <switch back to branch master or whatever one I’m working on>
- git read-tree --prefix=Source/Vendor/CocoaLumberjack/Framework -u 2.0.0-beta4:Framework

Is this a long-term solution? From my perspective, no. This is an initial step to getting CL 2.x support without changing too much of the directory structure. In the future I want to look into moving the SVGKit project into a separate 'Framework' Folder, and the demos into a separate folder, and just have those builds have respective podfiles for building.
Project-file updates to use updated lumberjack framework, just thinking about the OS X demo for now.
renaming to Lumberjack to CocoaLumberjack in pch
renaming DDLogC methods to DDLog, see cocoa lumberjack issue #220 for why this is okay.
rename of cocoalumberjack flag_info reference to lumberjack 2.x term
removing old lumberjack reference, should be referenced via pch file
hack: temporarily commenting out the internal log-level setting feature
minor, marking 'private' headers as private within OS X framework target build. This was an attempt to mitigate the intermitten build errors where "Duplicate Interface Definitions" occur..
rename of lumberjack header import in iOS pch file
project changes to make lumberjack work, essentially I dragged in the lumberjack framework projects (there's different ones for desktop & mobile) in the svgkit workspace.
adding a  deployment target minimum version for the ios demo, not exactly sure why I did this.
adding libCocoaLumberjack to be linked in the svgkit ios framework, but seems to be duplicated from two commits earlier. build of 'svgkit-ios framework' still broken
Merge remote-tracking branch 'origin/master' into Lumberjack-2.x-svgkit-MTSfork

Merged-together Files:
	Demo-OSX.xcodeproj/project.pbxproj
	Demo-iOS.xcodeproj/project.pbxproj
	SVGKit.xcodeproj/project.pbxproj
	Source/AppKit additions/SVGKImageRep.m

Files to be removed:
Source/Vendor/Lumberjack/CocoaLumberjack.h
removing earlier thought of having a separate svgklog file
Re-introducing 'rawLogLevel' support I temporarily commented out, updating it to work with Lumberjack 2.x conventions.
In svgkit.m LOG_OBJC_MAYBE (now legacy) is replaced with LOG_MAYBE - inserted extra 'tag' arg for lumberjack 2.x  (currently just nil)
removing 2.0.0-beta4 lumberjack installation for update to 2.0.0-rc
installation of Cocoalumberjack 2.0.0-rc - Classes - done via git read-tree --prefix=Source/Vendor/CocoaLumberjack/Classes -u 2.0.0-rc:Classes
installation of Cocoalumberjack 2.0.0-rc - Framework - done via git read-tree --prefix=Source/Vendor/CocoaLumberjack/Framework -u 2.0.0-rc:Framework