[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Build management (was: major design changes...can we)

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-05-21 22:42:47 CEST

Alan: great post. To some extent, my response is just a "me too" :-)

On Tue, May 21, 2002 at 09:22:54AM -0400, Alan Langford wrote:
> At 2002/05/21 09:54 +0300, Marc Girod wrote:
> >I believe nobody should care for yet another RCS. However smart.
>
> If the architecture crafted sufficiently well, should it not be possible to
> provide a layer that provides a "filesystem front-end" interface to
> Subversion? Then someone who wants to craft a ClearCase calibre build
> system on top of that is free to do so.

You betcha. And I totally believe that Subversion is built to do so. Our
libraries are a big win here. I've envisione quite a few apps that can be
built on top of SVN. I might even say some are "way cool" :-)

> Either way, a good, robust and complete version management system is an
> essential component of a much wider variety of downstream applications.
> Tightly integrated build management isn't all that useful if you're trying
> to get control of a sales team's proliferation of PowerPoint presentations.
> Most of the interface to a friendly sales-document management system will
> be useless for build management. But if both of those systems run off a
> single version control technology, it's a huge win for the people who have
> to maintain and support them.

I *completely* agree. Consider a web-based doc mgmt system. Hey! It gets to
use the same repository as what the developers are using. Oh, and the techie
developers can use 'svn co' to access the docs rather than that "slow-assed
web site the services guys put together" :-)

> Subversion's mission, as I see it, is to fix the things that are wrong with
> (or even irritating about) CVS (which implies some additional
> functionality). Period. End. Anyone on this list probably agrees that's a
> big enough job as it is.

You bet. "Can we replace CVS yet? Yes? Ship it." We can then start having a
lot of fun after that.

> The open development process makes the odds that
> Subversion will be structured so that it's useful as a base for more
> sophisticated tools (after all, if it isn't, then just restructure it so it
> is ;) ). If you want a killer build management tool with a robust, widely
> supported back end, start designing.

Yes. People can say, "Subversion should do <this> or do <that>," but I'll
always respond with "provide code" :-) Short of that, we're building a CVS
replacement.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 21 22:40:38 2002

This is an archived mail posted to the Subversion Dev mailing list.