I believe that CocoaPods address this concern via subspecs -
https://github.com/CocoaPods/CocoaPods/wiki/The-podspec-format
http://guides.cocoapods.org/making/specs-and-specs-repo.html
However, AIUI, this would require all Aerogear iOS related code to share one
Git repository or at least have some git submodules setup. Submodule setup will
be nasty for releasing new versions.
PodSpec guide additionally says that spec should include all subspec by default,
if user wants to be selective, he can do so by enumerating subspecs.
http://guides.cocoapods.org/syntax/podspec.html#default_subspec
My $0.02,
Karel
On Tue, 4 Feb 2014 09:11:27 +0100
Corinne Krych <corinnekrych(a)gmail.com> wrote:
Hello iOS folks
I’ve started looking at sync part, I’ve created a separate repo [1]. For now,
this lib is dependant on iOS-core. does is worth having it separate for folks
that what to use core without sync? Same question applies for encrypted
store. Right no encrypted store are part of iOS-core. do we want to separate
it for people who want core without encrypted store ? what about people who
all it all, encrypted store+sync, we’ll have to manage correctly transitive
dependencies. wdty?
++
Corinne
[1]
https://github.com/corinnekrych/aerogear-sync-ios
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev