Bob Archer <bob.arc...@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 BDB > > > 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. 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.
