newsSavane - News: Now using SVN as source code manager

Show feedback again
Latest News
New Savane release fixes symlink attack and privilege escalation posted by beuc, Wed 02 Dec 2009 10:24:18 PM UTC - 0 replies
Release 3.0: markup language and anti-spam tools posted by yeupou, Mon 04 Dec 2006 09:38:30 AM UTC - 2 replies
Release 2.0: interface heavy improvements, bugfixes and cosmetics posted by yeupou, Tue 03 Oct 2006 08:06:29 AM UTC - 2 replies
We need packagers! posted by yeupou, Tue 19 Sep 2006 06:09:45 PM UTC - 2 replies

Now using SVN as source code manager

Item posted by Mathieu Roy <yeupou> on Thu 10 Nov 2005 04:07:56 PM UTC.

We decided to change the sourcecode manager from CVS to SVN (see task #2229).

The CVS repository is still available through cvsweb at
It has been kept there for historical purpose.

See our project SVN page (link in the top menu) to obtain via SVN a copy of savane sourcecode. If you are not involved in Savane development, it may be best to use a packaged release (see in the Download Area, link in the top menu), more suitable for production use.

If you are not familiar with SVN, I suggest you take a look at


Message: 194
Easy move from CVS to SVN (posted by yeupou, Sat 12 Nov 2005 08:52:46 AM UTC)

If you have a production server running Savane from the CVS, you can easily switch to the SVN version by:

- moving the current savane directory, with CVS stuff, into somethingelse
- downloading anonymously the SVN into savane, exactly where the previous was
- copying configure.cache from the previous savane directory, with CVS stuff, "somethingelse", into the new savane directory
- in the new savane directory, running ./configure && make to regenerate things that requires it.

Thread Author Date
Easy move from CVS to SVNyeupouSat 12 Nov 2005 08:52:46 AM UTC


Post a followup to this message

You could post if you were logged in
Show feedback again

Back to the top

Powered by Savane 3.1-cleanup