With submodule support, Carthage is becoming increasingly useful for simply managing dependencies, and not always building them. This causes friction for new users, who may not know that a project uses the --no-build flag.
Some setting could maybe go into the Cartfile, but that quickly gets confusing. For example, what does it mean for a framework Cartfile to specify --no-build, but an application to specify --build? We don't really support mixing and matching like that.
Instead, maybe our philosophy for each command should be “do as little work as possible, unless more is requested,” which would be nice and UNIX-y too.
@Carthage/carthage Thoughts?
/cc @dannygreg @alanjrogers
With submodule support, Carthage is becoming increasingly useful for simply managing dependencies, and not always building them. This causes friction for new users, who may not know that a project uses the
--no-buildflag.Some setting could maybe go into the Cartfile, but that quickly gets confusing. For example, what does it mean for a framework Cartfile to specify
--no-build, but an application to specify--build? We don't really support mixing and matching like that.Instead, maybe our philosophy for each command should be “do as little work as possible, unless more is requested,” which would be nice and UNIX-y too.
@Carthage/carthage Thoughts?
/cc @dannygreg @alanjrogers