Subversion Post: 60602

Sponsored Content

Operating Systems Linux Subversion Post 60602 by cbkihong on Wednesday 19th of January 2005 09:33:20 AM

01-19-2005

Registered User

Subversion is my version control system of choice for managing the LaTeX sources of a book I am working on personally, though I store most of my other scripts or Web site content in CVS server instead.

Working with CVS command line options can be a horrendous experience for new users, as option values sometimes need to be given in certain order, or that the same switch may appears twice in a command but serving different purposes. e.g.:

cvs -d :pserver:anonymous@host:/home/cvsroot co -d tutorial/ tutorial

I am impressed by Subversion for a number of reasons:
- It has less tricky dark corners compared with CVS. CVS has certain behaviour that are not intuitive unless you have read the relevant sections of the manual.
- It supports file copy/rename without losing revision history. A feature I find most useful as I don't make good filenames usually at the very start.
- It does not distinguish binary/ASCII files. Some CVS front ends are prone to always add files in binary mode, making it difficult for some CVS clients to get context diffs even though it simply involves text data.
- Repository-wide revision numbers allow state at any instant to be consistently reproduced. With CVS, you can only be reliably achieving this by tagging often. Checkout by date/time with CVS does not necessarily produce a local copy at any consistent state, depending on the frequency of commits. Per-file revision is more intuitive IMO, though.

Personally I am more used to CVS, but I appreciate SVN's new features.

cbkihong

View Public Profile for cbkihong

Find all posts by cbkihong

5 More Discussions You Might Find Interesting

1. Solaris

Looking for a subversion GUI for Solaris 9

If available. Didn't see any on the tigris website. Don't have the programming experience to create one. Any third party software would do, too. Client isn't command line friendly.

2. HP-UX

Binaries/Depot for Subversion 1.4.3 for HP/UX 11.11

Could anyone help me out by providing binaries/depot for subversion 1.4.3? The hpux version is: HP-UX myhappybox B.11.11 U 9000/800 I am having trouble compiling the sources for hpux, the provided dependancies are extracted, but it continually falls over. We have previously had svn...

3. Linux

KDevelop And Subversion

Hi How I Can Configure KDevelop to Use A Subversion on Local Network System. When I Want to Create New Project, I See A Error With This Message: "Fail to create project directories on repository" What is My Problem??? Help Me Please!!! My KDevelop Version is: 3.0.5 My Subversion is: 1.5.0 ...

4. UNIX for Advanced & Expert Users

Problem with Subversion SVN

Hi, I am trtying to install SVN server with Apache. I have already configured apache with SVN modulesh and the same can be seen in the modules directory. -rwxr-xr-x 1 root root 34740 Jul 3 13:43 mod_authz_svn.so -rwxr-xr-x 1 root root 385133 Jul 3 13:43 mod_dav_svn.so now the...

5. Web Development

About Apache Subversion

Hi all, I have a trouble with this, the web server include a website and also config as apache subversion, this server crashed and i moved the HDD to another machine, i started all the services and the subversion worked fine, but when i access to the website, this message appear A username and...

LEARN ABOUT DEBIAN

cvs-debrelease

CVS-DEBC(1)						      General Commands Manual						       CVS-DEBC(1)

NAME

       cvs-debrelease - upload a cvs-buildpackage/cvs-debuild generated package

SYNOPSIS

       cvs-debrelease [cvs-debrelease options] [--dopts [dupload/dput options]]

DESCRIPTION

       cvs-debrelease  is run from the CVS working directory after cvs-buildpackage or cvs-debuild.  It uses the cvs-buildpackage system to locate
       the .changes file generated in that run.  It then uploads the package using debrelease(1), which in turn  calls	either	dupload  or  dput.
       Note  that  the	--dopts  option  must  be specified to distinguish the cvs-debrelease options from the dupload or dput options.  Also, the
       devscripts configuration files will be read, as described in the debrelease(1) manpage.

       Note that unlike cvs-buildpackage, the only way to specify the source package name is with the -P option; you cannot simply have it as  the
       last command-line parameter.

OPTIONS

       All  current  cvs-buildpackage options are silently accepted; however, only the ones listed below have any effect.  For more details on all
       of them, see the cvs-buildpackage(1) manpage.  All debrelease options (as listed below) are also accepted.

       --dupload, --dput
	      This specifies which uploader program to use; the default is dupload.

       -adebian-architecture, -tGNU-system-type
	      See dpkg-architecture(1) for a description of these options.  They affect the search for the .changes file.  They  are  provided	to
	      mimic the behaviour of dpkg-buildpackage when determining the name of the .changes file.

       -Mmodule
	      The name of the CVS module.

       -Ppackage
	      The name of the package.

       -Vversion
	      The version number of the package.

       -Ttag  The CVS tag to use for exporting sources.

       -Rroot directory
	      Root of the original sources archive.

       -Wwork directory
	      The full path name for the cvs-buildpackage working directory.

       -xprefix
	      This option provides the CVS default module prefix.

       --no-conf, --noconf
	      Do not read any configuration files.  This can only be used as the first option given on the command-line.

       --help, --version
	      Show help message and version information respectively.

SEE ALSO

       cvs-buildpackage(1), debrelease(1) and cvs-debuild(1).

AUTHOR

       cvs-buildpackage  was  written  by  Manoj  Srivastava, and the current version of debrelease was written by Julian Gilbey <jdg@debian.org>.
       They have been combined into this program by Julian Gilbey.

DEBIAN
								 Debian Utilities						       CVS-DEBC(1)