bsneed / modulo_objc Goto Github PK

• Create a module in THG/Shrubbery
• modulo update, so you have:
  • THG/Shrubbery
  • THG/CocoaLumberjack
• Decide you don't like this, and move Shrubbery to THG/modules/Shrubbery
• Delete the out of place CocoaLumberJack
• modulo update from THG/modules/Shrubbery
• Error reported:

Unable to proceed. The following modules have unpushed commits, stashes, or changes:
CocoaLumberjack

Key sourchPath is informational only. Let's change the name to reflect this. In addition, there is a ton of info that is ending up in README like all of the steps to add dependencies, linker, User Header Paths, etc. All of this should be reported when a module is added.

This also means that a missing info key would report nothing. This could be used to solve the CocoaLumberJack issue by something like:

modulo add lumberJackGitHubURL -embedded

that could make sure to NOT add that key to the lumberjack dependency, and thus not reported when someone adds this module.

modulo sync

// Removes unneeded dependencies

To be more in line with the naming of the project

Would be nice if the main ReadMe was a little more in depth and perhaps talked about why one would use modulo vs cocoa pods vs carthage.

or conversely, if initialBranch is missing, then git add of a module that does not have initialBranch in the dependencies tries to add --branch (null)

{
"dependencies" : [
{
"name" : "CocoaLumberjack",
"moduleURL" : "[email protected]:CocoaLumberjack/CocoaLumberjack.git"
}
],
"dependenciesPath" : "../",
"initialBranch" : "master",
"sourcePath" : "Shrubbery/THGLog.xcodeproj",
"name" : "Shrubbery"
}

will fail if someone tries to add this module to their project. However:

{
"dependencies" : [
{
"name" : "CocoaLumberjack",
"moduleURL" : "[email protected]:CocoaLumberjack/CocoaLumberjack.git"
"initialBranch" : "master",
}
],
"dependenciesPath" : "../",
"initialBranch" : "master",
"sourcePath" : "Shrubbery/THGLog.xcodeproj",
"name" : "Shrubbery"
}

works