Subversion - Revision history

Admin at 01:54, 15 December 2011

2011-12-15T01:54:34Z

← Older revision		Revision as of 01:54, 15 December 2011
Line 19:		Line 19:
	===SWIG===		===SWIG===

	SWIG provides language bindigns (see http://www.swig.org). Mac OS X (Snow Leopard) already ~~comes~~ with SWIG.		SWIG provides language bindigns (see http://www.swig.org).

			Mac OS X (Snow Leopard) and Ubuntu already come with SWIG.

	If you are interested in installing SWIG and do not have it already, you can find instructions in your subversion source directory, in:		If you are interested in installing SWIG and do not have it already, you can find instructions in your subversion source directory, in:
Line 48:		Line 50:
	--with-ssl \		--with-ssl \
	--without-berkeley-db \		--without-berkeley-db \
	--enable-swig-bindings=no \		--enable-swig-bindings=yes \
	--with-apxs=/path/to/apache/bin/apxs \		--with-apxs=/path/to/apache/bin/apxs \
	--with-neon=/usr/local \		--with-neon=/usr/local \

Admin: /* Configuration (1.7) */

2011-11-23T23:51:09Z

Configuration (1.7)

← Older revision		Revision as of 23:51, 23 November 2011
Line 86:		Line 86:
	CC="/usr/bin/gcc" \		CC="/usr/bin/gcc" \
	CXX="/usr/bin/g++" \		CXX="/usr/bin/g++" \
	\
	~~CXXFLAGS="-arch x86_64" \~~
	~~CCFLAGS="-arch x86_64" \~~
	</source>		</source>

Admin: /* Dependencies */

2011-11-23T23:21:41Z

Dependencies

← Older revision		Revision as of 23:21, 23 November 2011
Line 5:		Line 5:
	== Dependencies ==		== Dependencies ==

	~~To install subversion with the configure lines given below, I had to install [[~~Apache]] for the APR and APXS bindings, I had to install Neon for the http/https protocol (Neon is an HTTP and WebDAV client software), and I had to install Python bindings to use a [[Trac]] wiki with Subversion.		===Apache===

	I ~~installed Apache following this page:~~ [[Apache]]		I had to install [[Apache]] for the APR and APXS bindings.

	~~Neon was installed to /usr/local with SSL, using the configure line given here:~~ [[~~Neon~~]]		See [[Apache]]

	~~The Python bindings required swig, which~~ I ~~already~~ had ~~as part of~~ Mac OS X (if you are interested in installing SWIG and do not have it already, you can find instructions in your subversion source directory, in:		===Neon===

			I had to install Neon to use the http/https protocol in SVN. Neon is an HTTP and WebDAV client software. I installed it to /usr and installed with SSL.

			See [[Neon]]

			===SWIG===

			SWIG provides language bindigns (see http://www.swig.org). Mac OS X (Snow Leopard) already comes with SWIG.

			If you are interested in installing SWIG and do not have it already, you can find instructions in your subversion source directory, in:

	<pre>		<pre>
Line 17:		Line 27:
	</pre>		</pre>

	This describes the steps for installing ~~Python~~ language bindings.		This describes the steps for installing SWIG and language bindings.

			===SQLite===

	I also had to install sqlite, which involved basically downloading the "amalgamation" from SQLite's website, then moving sqlite3.c into the subversion source as specified by svn's configure. I'm not sure what the .c file does, but it basically takes care of the sqlite dependency.		I also had to install sqlite, which involved basically downloading the "amalgamation" from SQLite's website, then moving sqlite3.c into the subversion source as specified by svn's configure. I'm not sure what the .c file does, but it basically takes care of the sqlite dependency.

Admin: /* Configuration (1.7) */

2011-11-23T23:17:31Z

Configuration (1.7)

← Older revision		Revision as of 23:17, 23 November 2011
Line 58:		Line 58:
	<source lang="bash">		<source lang="bash">
	./configure \		./configure \
	--prefix=$HOME/pkg/svn/1.7.1 \		\
	--with-ssl \		--prefix=$HOME/pkg/svn/1.7.1 \
	--without-berkeley-db \		\
	--with-swig \		--with-ssl \
	--with-apxs=$HOME/pkg/apache/std/bin/apxs \		--without-berkeley-db \
	--with-neon~~=/usr/local~~ \		--with-swig \
	--with-apr=${HOME}/pkg/apache/std \		\
	--with-apr-util=${HOME}/pkg/apache/std		--with-apxs=$HOME/pkg/apache/std/bin/apxs \
			\
			--with-neon \
			\
			--with-apr=${HOME}/pkg/apache/std \
			--with-apr-util=${HOME}/pkg/apache/std \
			\
			CC="/usr/bin/gcc" \
			CXX="/usr/bin/g++" \
			\
			CXXFLAGS="-arch x86_64" \
			CCFLAGS="-arch x86_64" \
	</source>		</source>

Admin: /* Configuration (1.7) */

2011-11-23T22:22:04Z

Configuration (1.7)

@@ Line 72: / Line 72: @@
 <pre>
 LIBS="-lcrypto -lssl" ./configure \
 </pre>

Admin at 21:48, 23 November 2011

2011-11-23T21:48:16Z

@@ Line 3: / Line 3: @@
 = Installation =
-== Configuration ==
+== Dependencies ==
 I configured subversion version 1.5.2 with the following configure line:
@@ Line 27: / Line 45: @@
 I have to point subversion to apache so that it can handle subversion repository addresses that begin with <code>http://</code> or <code>https://</code> (as opposed to the default <code>svn://</code>, which works fine out of the box).
-== Dependencies ==
+I then ran
-To install subversion with the above configure line, I had to install [[Apache]], and I also had to install Neon, which is an HTTP and WebDAV client software.  It is required for the <code>http://</code> and <code>https://</code> repository addresses.  It's available from http://www.webdav.org/neon/.  I install it to <code>/usr/local/</code>, and without any particularly special configure line (just <code>./configure</code>).
+If you run into problems with OpenSSL or other SSL-related things, try changing the first line of this to:
-I also had to install sqlite, which involved basically downloading the "amalgamation" from SQLite's website, then moving sqlite3.c into the subversion source as specified by svn's configure. I'm not sure what the .c file does, but it basically takes care of the sqlite dependency.
+<pre>
 = SVN Guide =

Admin at 18:13, 23 November 2011

2011-11-23T18:13:18Z

@@ Line 368: / Line 368: @@
 The following guide covers how to set up a subversion server, and how to create new repositories in the server.
 ==Setting up a new SVN server==
@@ Line 375: / Line 376: @@
 To run a computer as an SVN server, you need to first install SVN, then open port 3690 on the machine that will be the SVN server, in case there is any firewall on that machine. Port 3690 is the port that is used by the SVN server and clients to communicate.
-Once you do these things, you can create a repository using the <code>svnadmin</code> command, as described below.
+Once you do these things, you can create a repository using the <code>svnadmin</code> command, as described in the next subsection.
 The visibility of the SVN server depends on the visibility of your machine (specifically, port 3690). Details are described below.
@@ Line 410: / Line 411: @@
 This can be done from behind a network as described in the previous section, by rerouting traffic to a certain port on the router to a certain port on the computer that is the SVN server (typically 3690 to 3690, but it may be of interest to use a non-default port).  If the computer has a public IP address, making an SVN server accessible to the public is a simple as installing SVN and opening port 3690.
 ==Using SVN Server Securely==
@@ Line 463: / Line 495: @@
 * access over http/dav, no https - http://csoft.net/docs/svndav.html.en

Admin: /* Dependencies */

2011-11-23T18:10:30Z

Dependencies

← Older revision		Revision as of 18:10, 23 November 2011
Line 30:		Line 30:

	To install subversion with the above configure line, I had to install [[Apache]], and I also had to install Neon, which is an HTTP and WebDAV client software. It is required for the <code>http://</code> and <code>https://</code> repository addresses. It's available from http://www.webdav.org/neon/. I install it to <code>/usr/local/</code>, and without any particularly special configure line (just <code>./configure</code>).		To install subversion with the above configure line, I had to install [[Apache]], and I also had to install Neon, which is an HTTP and WebDAV client software. It is required for the <code>http://</code> and <code>https://</code> repository addresses. It's available from http://www.webdav.org/neon/. I install it to <code>/usr/local/</code>, and without any particularly special configure line (just <code>./configure</code>).

			I also had to install sqlite, which involved basically downloading the "amalgamation" from SQLite's website, then moving sqlite3.c into the subversion source as specified by svn's configure. I'm not sure what the .c file does, but it basically takes care of the sqlite dependency.

	= SVN Guide =		= SVN Guide =

Admin at 09:51, 24 October 2011

2011-10-24T09:51:58Z

← Older revision		Revision as of 09:51, 24 October 2011
Line 1:		Line 1:
			For a more advanced guide to using Subversion, see [[Subversion Beyond the Basics]] page

	= Installation =		= Installation =

Admin: /* Setting up a new SVN server */

2011-10-24T08:52:37Z

Setting up a new SVN server

← Older revision		Revision as of 08:52, 24 October 2011
Line 406:		Line 406:

	This can be done from behind a network as described in the previous section, by rerouting traffic to a certain port on the router to a certain port on the computer that is the SVN server (typically 3690 to 3690, but it may be of interest to use a non-default port). If the computer has a public IP address, making an SVN server accessible to the public is a simple as installing SVN and opening port 3690.		This can be done from behind a network as described in the previous section, by rerouting traffic to a certain port on the router to a certain port on the computer that is the SVN server (typically 3690 to 3690, but it may be of interest to use a non-default port). If the computer has a public IP address, making an SVN server accessible to the public is a simple as installing SVN and opening port 3690.

			==Using SVN Server Securely==

			To use an SVN server securely, you can use SVN over SSH by giving the address of the SVN repository like this:

			<pre>
			$ svn info svn+ssh://address/repository
			</pre>



			==Configuring SVN over HTTP/HTTPS==

			Some repositories have an address using <code>http://address</code> or <code>https://address</code> instead of <code>svn://address</code>. This is because the SVN server has been configured to be used over HTTP or HTTPS.

			Once you have a repository created and set up, and you can access it using a <code>svn</code> or <code>svn+ssh</code> prefix, you can convert it to using a <code>http</code> or <code>https</code> prefix by doing the following:

			'''Step 1. Modify httpd.conf'''

			The [[Apache]] httpd.conf file should include the DAV and AUTHZ modules:

			<pre>
			LoadModule dav_svn_module libexec/apache2/mod_dav_svn.so
			LoadModule authz_svn_module libexec/apache2/mod_authz_svn.so
			</pre>

			And the location of the repository set up to be accessed via SSH:

			<pre>
			<Location /repo>
			DAV svn
			SVNPath /usr/local/repo
			</Location>
			</pre>

			One website [http://www.sonzea.com/articles/subversion-trac.html] advises putting these new directives into a file called <code>httpd-subversion.conf</code> and then including that in the main <code>httpd.conf</code> file by adding this line:

			<pre>
			Include /path/to/apache/conf/httpd-subversion.conf
			</pre>

			To use HTTPS, you have to set up an SSL certificate for your server; to figure out how to do that, try these resources:
			* http://www.tc.umn.edu/~brams006/selfsign.html
			* http://www.sonzea.com/articles/subversion-trac.html




			=Resources=

			* Guide for doing this on Leopard with HTTP ''and'' HTTPS, with instructions on SSL certificates, etc - http://www.sonzea.com/articles/subversion-trac.html

			* access over http/dav, no https - http://csoft.net/docs/svndav.html.en

	==Creating a new repository ==		==Creating a new repository ==