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

Re: Subversion implementation

From: Nico Kadel-Garcia <nkadel_at_comcast.net>
Date: 2006-08-10 21:26:55 CEST

Ryan Schmidt wrote:
> On Aug 10, 2006, at 16:49, Dennis.Burke@apcc.com wrote:
>
>> We have been using Subversion 1.1 with Apache 2.0. on W2000 server
>> using
>> Berkely DB for the repository and have had a great deal of success
>> over the
>> past several years. Thanks for all of your help and hard work. We
>> have benefited a great deal from your efforts.
>>
>> We are looking to upgrade our system in the following areas and
>> would like
>> recommendations from users regarding the potential for continued
>> success in
>> our plans for expanding our change management system.
>>
>> 1. Our new installation will be hosted on Redhat Enterprise Linux
>> 4. We
>> expect to use Apache 2.2.3 and Berkely DB based on proven
>> reliability. What is the latest, stable, recommended Subversion
>> binary currently available for this implementation?
>
> David Summers provides binaries of the current version of Subversion,
> 1.3.2, for RHEL4 but it does not include BerkeleyDB support. Many
> people have had problems with BDB and it's just simpler to leave it
> out.
> http://subversion.tigris.org/project_packages.html#redhat-fedora
>
> If you insist on BDB, you can build Subversion 1.3.2 yourself.

It's the RHEL3 version that doesn't provide BDB support: getting a recent
enough version of BDB integrated into RHEL3 is awkward at best, dangerous at
worst. David's SRPM's don't yet have the 64-bit patch built-in, but should
with the next release.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 10 21:28:12 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.