Re: Project- vs. Package-Level Branching in Git
- From
- Enrico Weigelt <weigelt@metux.de>
- Date
- Jan 29, 2011, 19:33 UTC
- Message-ID
- <20110129193323.GD602@nibiru.local>
- In-Reply-To
- <15B7CA2E-C584-4563-B9E3-D80861CD9565@shaggyfrog.com>
* Thomas Hauk <tom@shaggyfrog.com> wrote:
> 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.
No, just leave them as they are: separate packages. Period. Let a dist buildsystem handle the project's build process, including dependency resolving, packaging, etc.
> Git just doesn't seem to scale when it comes to componentized > projects.
These "componentized" projects (as you call it - I'd rather call it the exact opposite) suffer from an ideology that doens't know to differenciate between the fundamental stages of an software building up to deployment, they try do to everything in one fat blob - that's why fail or burn expensive resources frequently. (I've seen that often enough in my last 15 years of software engineering ...)
cu
-- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: weigelt@metux.de mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ----------------------------------------------------------------------