Package svn-0.33.1-1

10.11/x86_64

1.9.3-1

 

 

 

10.10/x86_64

1.9.3-1

 

1.9.3-1

 

10.9/x86_64

1.9.3-1

 

 

 

10.8/x86_64

1.9.2-1

 

1.8.14-1

 

10.7/x86_64

1.9.2-1

 

 

 

10.6/x86_64 *

1.7.13-1

 

 

 

10.6/i386 *

1.7.13-1

 

 

 

10.5/i386 *

1.7.10-2

 

1.4.4-11

 

10.5/powerpc *

1.7.10-2

 

1.4.4-11

 

10.4/i386 *

1.7.11-1

 

 

 

10.4/powerpc *

1.7.11-1

 

1.2.3-1012

 

10.3/powerpc *

1.4.4-1

1.4.4-1

1.1.3-12

 

10.2-gcc3.3/powerpc *

 

1.1.2-1

 

 

10.2/powerpc *

 

0.32.1-1

 

 

10.1/powerpc *

 

 

 

 

The goal of the Subversion project is to build a version control system that is a compelling replacement for CVS in the open source community. Why should I switch to Subversion, after all CVS is the standard? Some advantages of Subversion include: - Commits are atomic - Moving and renaming are versioned. - Working with directories are easy. E.g. adding a directory adds all sub-files and folders to the repository. - It is fast: branching and tagging are cheap (constant time) operations, client/server protocol sends diffs in both directions, and in general time are proportional to change size, not project size. - Meta-data is versioned per file, e.g. store the `execute' permission flag on files in the repository. - Efficient handling of binary files - it uses a binary diffing algorithm to transmit and store successive revisions. Is Subversion stable enough for me to use for my own projects? The Developers think so! Read the full FAQ answer on the website: <subversion.tigris.org/project_faq.html#stable> Subversion is broken into these packages in fink: (the -ssl variants enable ssl encryption) - The "svn-client" package installs a comman-line client program for using subversion. - The "svn" package installs a stand-alone server 'svnserve'. Install this package if you want to maintain a stand-alone server. - The "libapache2-mod-svn" package contains an apache2 module to enable serving a repository via web-dav. - The "svn-shlibs" package contains the shared libraries for the other packages. It is installed automatically by fink when needed. - The "svn-dev" package contains the development headers and libraries. It is installed automatically by fink when needed. WARNING: *** Subversion is alpha code right now. *** For More Information, check the main Subversion website below and read the book at <svnbook.red-bean.com/> Also look in /sw/share/svn/notes and /sw/share/svn/contrib

Type 'svnserve --help' or 'svnadmin help' for usage. Some tools (e.g. cvs2svn) and examples are stored in /sw/share/svn/tools PLEAE NOTE: In order to make commits more responsive, repository deltification is no longer automatic. However, you may want to run deltification as a background process in your repository post-commit hook. For example, the new post-commit.tmpl file recommends 'nice -2 svnadmin deltify "$REPOS" -r "$REV" &'. NOTICE: ##################################################################### ## WARNING WARNING WARNING WARNING WARNING WARNING WARNING ## ##################################################################### ## ## ## The 0.28 releases did an incompatible change to the Subversion ## ## repository filesystem schema. Repositories created with ## ## Subversion code prior to 0.28 will unable to operate ## ## with this new code. To maintain the ability to use said ## ## repositories, you must use a version 'svnadmin dump' prior to ## ## this change to dump your repository to a dumpfile, then use ## ## this new Subversion code to create, and load your dumpfile ## ## a new repository using 'svnadmin load'. And don't forget to ## ## copy over any custom configuration/hooks from the old to the ## ## new repository. ## ## ## ##################################################################### Please see the notes/repository_upgrade_HOWTO document for documentation on migrating pre-0.28 repos to an updated version. Also located here: <svn.collab.net/repos/svn/trunk/notes/repos_upgrade_HOWTO>