Public SourceMage Discussion List

["Sergey A. Lipnevich" <sergeyli AT pisem.net>]

First of all, I support your decision to abandon the "now rotten"
repository, although I'm now up against the task of migrating my
working copies (three of 'em) changes to P4 working copy.

I don't use any GUI in my work on SourceMage, because I do 70% of it in
a terminal session. That doesn't mean I don't enjoy WinCVS (and CVSNT)
at work, which has its limitations anyway. Firstly, I would suggest
against using a cvs GUI tool and configuring svn as a kind of "external
cvs binary". The more specific the tool will be about the cvs
command-line options, the worse. I read Subversion's list selectively
but regularly, meaning several times a week, and I don't remember
anyone using it this way. Secondly, here's a (short) list of
Subversion's GUI tools:

Name/URL	Official description	My Comment
gsvn	GTK GUI Client for the Subversion version control system	As far as I can tell the most actively developed 'cause  it's maintained by Subversion developers. Written in Python and requires py-gtk bindings. That project would be my first bet.
RapidSVN	Cross-platform GUI front-end for the Subversion revision system	Uses wxWindows (wxGTK spell), has a spell in Sorcery by yours truly. No visible activity detected for, I'd say, months, after Alpha 1 had been releasedon Oct 15 last year. What can I say? It works but lacks many features.
JSVN	The goal of JSVN is to develop a Java Swing client to access and manipulate a Subversion repository	Know very little about it. Released version 0.1.2 very recently.
ViewCVS	Read-only GUI for CVS and Subversion repositories	To get the Subversion functionality take the latest 1.0-dev source from SourceForge's CVS repository.
TortoiseSVN	TortoiseSVN is a total rewrite of TortoiseCVS using C++ to support the Subversion version control system	Yeah, it's for Windows, but I include it for completeness. They released the first public version less than a week ago.

Another point: Subversion does require Berkeley DB 4.1. I personally
had a huge problem with version 4.1's desire to use direct I/O deafure
of the Linux kernel, but finally I patched it and everything's OK with
my machines now, all software that needs db is using 4.1. Another piece
of news, this time a good one, is that if anyone relies on an RPM- or
APT-based package management on some of their systems, both packages
are maintained fairly good, with RPM probably leading -- usually they
publish RPM within a day or two from the new release.
The tools
directory of Subversion's repository has many well-used scripts that
were developed by Subversians themselves, including more-or-less
working cvs2svn, backup scripts, commit access control, etc. There's
yet to be support for client certificates (similar to SSH) for
authentication over HTTP, but they're closing in on it. Meanwhile,
basic password authentication over HTTPS is in place and works well.
That's why it's not practical to allow commits over HTTP (reads can be
anonymous, no problem), only HTTPS.
So fas so good, let me know if there are more questions.

Sergey.

Eric Schabell wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sergey,
>
> One quick question, is it CVS compatible in the sense that our users can use 
> the provided gui's (cervisia and such)?
>
> The decision will be made later after we find someplace to host it, the move 
> away from cvs is temperary as stated in my postings.... we only moved as 
> there is no further admin access to our current host and I don't want 
> development to stop.
>
> I am working on a more permenent solution....
>
> - -- 
> /*
>  * Eric D. Schabell M.Sc.
>  *   Project Lead Source Mage GNU/Linux
>  *   SourceMage: http://www.sourcemage.org
>  *   Shopping: http://www.cafeshops.com/cp/store.aspx?s=sourcemage.0
>  *   irc.openprojects.net (#sourcemage)
>  *   nick -> erics
>  */
>
>
> > On Wednesday January 29 2003 06:32, Sergey A. Lipnevich wrote:
> > Hi All,
> >
> > Adding to the urgent migration away from CVS, I wanted to suggest
> > evaluating Subversion. I'm willing to perform the setup and customize
> > all the commit scripts as necessary. There are two options: I may have
> > time and energy to persuade my management to allow our repository to
> > remain on our server (which will also mean Bugzilla, ViewSVN - a ViewCVS
> > for Subversion, beautiful Horde/IMP webmail for gurus, and hot cocoa
> > every morning... maybe  :-) ), and setup the project. That was option
> > number one, not realistic for at least two weeks. Another option is that
> > I can setup Subversion on a system having an Apache 2.0.44 and some
> > libraries, and a local SMTP gateway for diff messages, provided that I
> > haveSSH access, if such system will be provided by someone else.
> > To temper your skepticism, please have a closer look at the Subversion's
> > list of active public repositories here:
> > http://subversion.tigris.org/svn-repositories.html. Many of these
> > projects accumulated sufficient knowledge of how to deal with Subversion
> > in a production environment, notably the "IEEE 1394 for Linux" project
> > http://www.linux1394.org/, which includes one of the Subversion
> > developers (or Subversion includes one of the Linux1394 developers, your
> > call). Practical advice on Subversion can be found here:
> > http://www.linux1394.org/svn.html, and a big book of advice is here:
> > http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=256.
> > Be judgemental but technical in your feedback ;-), thank you very much!
> >
> > Sergey.
> >
> > _______________________________________________
> > SM-Discuss mailing list
> > SM-Discuss AT lists.ibiblio.org
> > http://lists.ibiblio.org/mailman/listinfo/sm-discuss
> >   
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQE+N4aaruUhvfIGbDIRAsDfAKCThgixD2+FWSKyHX/GAex0aoPKgACdFisb
> KA2dC2rdzVlvFAgbX4JkvIE=
> =BI9P
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss