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

Re: Subverting Sourceforge...

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-02-14 16:42:25 CET

David Bovill <david.bovill@opn-technologies.com> writes:

> >> "OK, everyone wants / expects CVS access, but I can justify going down
> >> the Subversion root at this stage because I can mirror to CVS and provide
> >> anonymous CVS access on Sourceforge."
> >
> > Sure, this is easy to do with any SCM system, as long as the system
> > has 'post-commit' hooks. Subversion's own repository has a
> > post-commit hook script that mails out a unified diff of the commit's
> > changes to all svn developers. You could tweak that script to apply
> > the very same diff to a CVS working copy and run 'cvs commit'. It's a
> > no-brainer.
> It is a lot easier to install Apache modules with an ISP than CVS - so
> anyone have any suggestions as to how to get Subversion to update a CVS
> Sourceforge repository automatically?
> An ideal would be a built in commit_to_cvs module - no fancy stuff, that
> would all be done in Subversion. Another option is to have a public service
> / web service for this...

I don't understand: why do you think you need a module? Is there
something insufficient about the solution I described above?

  * make a sourceforge project.
  * check out a CVS working copy of your project.
  * do all your work in a Subversion repository.
  * whenever you commit to Subversion, a post-commit hook script
    patches your CVS working copy and commits the changes to the
    Sourceforge repo.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:07 2006

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.