Re: Build management

Hi,

>>>>> "AL" == Alan Langford <jal@ambitonline.com> writes:

AL> If you want a killer build management tool with a robust, widely
AL> supported back end, start designing.

Right. I know. This is the rule of the game.

Now tell me why should I do it _on top of subversion_? And e.g. not on
arch, katie, Elephant File System, CVFS, Moraine or whatever, or even
from scratch?

Before I would jump into such a huge investment, I'd rather make sure
sure there is a community to join. In fact, there is an annoying lack
of "continuity" that would typically prevent this kind of contribution
(not just "scratching one's itch").

And of course, nothing says I'd have either the skills or the time.

AL> Tightly integrated build management isn't all that useful if
AL> you're trying to get control of a sales team's proliferation of
AL> PowerPoint presentations.

Two answers to that:
- I think you are fooled by the words "build management", which are
  only an accident of history. What is at stake might be as wide as
  dependency auditing, or generic (and thus partial) structuring of
  information.
- One shouldn't try to fight people willing to avoid collaboration.
  Producing PowerPoint slides is a choice: creating artifacts instead
  of maintaining information. The motivation is partly romantic, and
  driven by metaphors of the past: the individual artist, general or
  hero.

-- 
Marc Girod        P.O. Box 323        Voice:  +358-71 80 25581
Nokia NBI         00045 NOKIA Group   Mobile: +358-50 38 78415
Takomo 1 / 1c47   Finland             Fax:    +358-71 80 61604
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org