From: Paul Duncan <pabs@...>
Date: 2007-07-23T22:41:06+09:00
Subject: Re: svn+http on RubyForge

--aVD9QWMuhilNxW9f
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Tom Copeland (tom@infoether.com) wrote:
> On Sun, 2007-07-22 at 06:10 +0900, Tomas Pospisek's Mailing Lists wrote:
> > On Sat, 21 Jul 2007, Tom Copeland wrote:
> >=20
> > > Just wanted to let folks know that RubyForge now supports svn+http for
> > > read-only access to the svn repositories.
> >=20
> > Nice, thanks! I had to "tunnel" through our own server in order to=20
> > checkout the current rubyforge mocha project at my current contract wor=
k.=20
> > It took me several calls, some month and a half of waiting and a formal=
=20
> > request for my client company to open the SVN port and then only to my =
own=20
> > machine ... ;-). Life will be easier now.
>=20
> Cool.  I hope to get svn+https up and running at some point too.  As far
> as I can tell, it seems like svn+ssh and svn+https are mutually
> exclusive for the same svn repo - either the filesystem has to handle
> the permissions or mod_dav_svn has to.  I'm working on a automated way
> for a project admin to elect one or another... we shall see....

Try using mod_auth_pam to defer HTTP authentication to PAM; then people
don't have to pick and choose.

> Yours,
>=20
> Tom
>=20
>=20

--=20
Paul Duncan <pabs@pablotron.org>        pabs in #ruby-lang (OPN IRC)
http://www.pablotron.org/               OpenPGP Key ID: 0x82C29562

--aVD9QWMuhilNxW9f
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGpK/uzdlT34LClWIRAs1gAJ9e8hfSEEQs9Clz0y4ALJ+GoGJgpgCfcYc2
8w3jmdVOMZ95BYvuO1gLXWw=
=9j+C
-----END PGP SIGNATURE-----

--aVD9QWMuhilNxW9f--