Victor Lowther (victor.lowt...@gmail.com) wrote: > This is intended to work as a starting point for a discussion of what tool > we should use to use to track inter-repository dependencies for CB2.0 in > the opencrowbar org.
Before evaluating the tools I think it would be worth trying to clarify the requirements. For example, all the approaches you list seem to assume that there will only be dependencies from a single superproject repository onto multiple slave repositories, but why is it safe to exclude the possible need to track dependencies between slave repositories? What do these repositories contain? Multiple barclamps in the superproject and one per slave? Where do tools live? Is there a genuine need to track the dependencies using git _meta_data, or could it be done by representing them within (say) a text file which is then tracked by git, in the same way that bundler does it with a Gemfile? I have a strong preference for reusing existing technology over rolling custom tools. For example, packaging barclamps as gems would provide the functionality of the whole gem/bundler ecosystem for free, which AFAICS would in one stroke solve the whole problem. > I expect the outcome of this discussion to be > relevant no matter what we eventually wind up doing, do please leave your > opinions about migrating to a different org somewhere else. Agreed, that's an entirely separate discussion. _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
