[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Tigris binary packages for Windows

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Wed, 3 Mar 2010 17:42:49 -0500

> Bob Archer <Bob.Archer_at_amsi.com> wrote on 03/03/2010 03:15:22 PM:
> > > David Darj wrote:
> > > > My plan was to build (for a start) what's included in the
> > > > svn-win32-1.6.x.zip,
> > > >
> > > > Win32 binaries (svn, svnadmin, svnserve, svnmucc, etc...) both dor
> > > > and FSFS, including OpenSSL
> > > > Modules for Apache 2.2.x (mod_dav_svn.so, mod_authz_svn.so)
> > > >
> > > > in short: what's needed for building the Windows msi installer.
> > > >
> > > > /David
> >
> > > Yes, that's exactly what I had in mind.
> > > As to the "extract collabnet and repack" idea, I too am not sure if it
> > > would be allowed
> > >
> >
> > What is wrong with the collabnet installers/binaries that you can't use
> them?
> Different default installation path and the old tigris installer
> needs to be manually removed.  The collabnet one can install more stuff
> (including apache) which I wouldn't want to give as an option.


1. You only have to remove the tigris installer once.
2. You can specify the install directory rather than accept the default. When you run upgrades it will maintain the INSTALLDIR that you used.
3. It only "installs" apache if you select it. And you can also opt to not set up svnserver/apache as services if you have you own apache install you want to use. Yes it throws apache in there too... 20 MB or so. You can delete it if taht 20 MB really bothers you. You could create a batch file that deletes all of the apache stuff except mod.dav_svn.so and run it after you run the installer.

There is also the client only installer which doesn't install any of the server side stuff.

> I'm willing to move to another installer for our enterprise users
> for a "major" 1.7 upgrade, but hesitant to do it sooner.
> My other option is to just modify the TortoiseSvn installer to
> include command line binaries from somewhere.  (This wouldn't
> be for outside distribution though, so wouldn't help the community.)
> Kevin R.

If you want just the command line binaries, use the client only collabnet installer.

I really haven't seen a show stopper with using the collabnet installers except for, what seem to me, like a few very minor nits.

Also, maybe if you ask collabnet to modify their install a bit so you can have it give you mod_dav_svn.so without all the other apache stuff they might be willing to do that.

Received on 2010-03-03 23:42:29 CET

This is an archived mail posted to the Subversion Users mailing list.