Re: Project- vs. Package-Level Branching in Git

On Jan 27, 2011, at 12:53 PM, Ævar Arnfjörð Bjarmason wrote:

But how often do you have a project that has no external or internal dependencies on any other packages or libraries? Any project I've ever done, big or small, has relied on some existing codebase. Imagine a project that uses liba and libb, which both reference libc. To use Git, I'd have to have copies of libc existing in three repositories, and copies of liba and lib in two repositories each. What a nightmare... and that's only a trivial hypothetical example.

I understand that Git was designed with a specific feature set in mind -- to manage Linux kernel development -- and as such isn't going to satisfy everyone. But I'm having trouble figuring out how to integrate it as the SCM in my projects, which aren't organized any differently than any other projects I've seen. Surely I can't be the only person with these difficulties? Git just doesn't seem to scale when it comes to componentized projects. Do other distributed VCSs work better than Git in this respect?

I'm really trying to get on the Git bandwagon, here.

-- Thomas Hauk Shaggy Frog Software www.shaggyfrog.com