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

Re: integrating Subversion with a build tool?

From: Timothee Besset <ttimo_at_idsoftware.com>
Date: 2003-03-23 12:51:55 CET

Since I know a bit of both worlds ..

One of the main design differences of SVN compared to CVS is that
revisions are atomic through the whole repository. This is really at the
base of SVN's design. I don't know exactly how the source control is
described in SCons (since that part is not released yet :) ), but maybe
things should be done a bit differently at SCons level? Reflecting the
fact that the basic checkout unit in SVN is the directory?

Otherwise I suppose svn cat would be a solution. SVN has python bindings
though, if you are spawning svn commands, you should use the SVN python
bindings instead, I suppose that would give you a lot more freedom?

TTimo

On Sat, 22 Mar 2003 15:43:35 -0600 (CST)
Steven Knight <knight@baldmt.com> wrote:

> Hi. I'm the project leader for SCons (http://www.scons.org/), a
> Python-based build tool with a number of cool features.
>
> I'm going to be rolling out our next version soon (I hope this week)
> with support for fetching files from a number of source code management
> systems, including SCCS, RCS, BitKeeper, CVS and Perforce. I'm hoping
> to also support Subversion, but I'm runnning up against the apparent
> design decision to only support checkouts of entire directories, not
> individual files.
>
> GNU Make (et al.) supports a widely-used automatic ability to check out
> individual source files from SCCS and RCS if a local copy file doesn't
> already exist. I've implemented a similar feature in SCons, extending
> it to also support BitKeeper and CVS.
>
> The best idea I've been able to come up with for Subversion is to use
> "svn cat" to redirect the current contents to the local file. This
> works, but it's still kind of a lose because it's not a real checkout.
> People wouldn't be able to then work with the file(s) and check them in
> like they're used to with other source code systems.
>
> Of course, I've only used Subversion enough for my own testing purposes,
> so I'm probably overlooking some other bright way to do this. Are
> there any other build tools out there that support automagic Subversion
> checkouts? Can anyone give me any good ideas for other ways I can
> support this in a way that's more natural for Subversion's design?
>
> I'm not on the Subversion list, so please keep me CC:ed on any replies.
>
> Thanks!
>
> --SK
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Mar 23 12:52:52 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.