Hi Stefan,

You can use MonticelloCVS, although it's not being actively maintained 
anymore.  You might have to use an old version of Monticello to make it 
work or I imagine it could probably be updated easily to work with the 
newest MC if you wanted (we'd happily take a patch for that).

MCCVS is basically a backwards compatibility layer for the old 
monticello file format which was designed to go into CVS (but svn would 
work fine too).  It outputs all the code in the package into a single 
file in an ordering designed to minimize change and thus minimize the 
diffs in CVS and thus minimize the chance of unecessary conflicts.

Once the new MC with repositories had been written, though, we basically 
stopped doing anything with the compatibility layer because it doesn't 
end up being nearly as pleasant an experience (MC can do much smarter 
calculations with the ancestry tree).

I imagine one *could* probably write an SVN repository client for MC 
using DAV... you could probably build up versions a little more 
dynamically by taking the ancestry, commit logs, and UUIDs from the svn 
repository.  But, none of us needing to use SVN, I don't think it's high 
on anyone's radar.  I'd be happy to provide a few pointers if you wanted 
to take it on though... <shrug>

Julian

Stefan Krecher wrote:
> Hi,
> 
> i got a question regarding Squeak-Sourcecode-Management.
> Parts of a current project i'm working on are developed with Squeak,
> other parts with Java, C and C++.  All Sources of the project are
> managend in a svn-repository. I used to check in the Squeak-Changesets
> but actually i'm looking for a better way to do the
> source-code-management.
> Is there a way to directly work with svn with squeak? Are there better
> ways to manage sources? Could Monticello somehow be integrated with
> svn?
> 
> Thank in advance for any suggestions,
> Stefan
> 

-- 
   Julian Fitzell  --  Beta4 Productions
julian at beta4.com  --  http://www.beta4.com
Seaside: http://seaside.st/