On 11/15/2010 9:17 AM, Edward Ned Harvey wrote:
>>> On RHEL4 / RHEL5, I find it ridiculously easy to build svn from source.
>>> Here is my build script:
>> Great: now reliably provide HTTP/HTTPS access for offsite repository use,
>> configure mod_dav_svn for local HTTP and HTTPS server usage, utilities
>> configuration files, and assure that ssn+ssh discovered all the necessary
>> libraries. Oh, you didn't have the include files installed for those and
>> therefore ./configure didn't detect them?
>> Whoops! Guess those parts all got left out of our script! And don't forget
>> sqlite version issues!!!
> Yikes, somebody doesn't mind taking a dump in public!
> All I got to say is:
> (a) works for me (including http& https) ... we don't use svn+ssh but I see
> no reason it wouldn't work ... I know nothing of any sqlite issues you
> allude to (nor do I care), so please put in the level of effort necessary
> for things to work for you in your environment,
> (b) other than building from source, there's no better way that I know to
> get the latest svn 1.6 in rhel4 / rhel5. AKA, there are no rpm's available
> that I know of, which I trust more than building from source as described.
Has someone had specific problems with the rpmforge rpms? I've been
using them on centos5 without any trouble, although I don't keep the
repository enabled during system updates to avoid pulling in other
packages that might conflict with the base versions. The only quirk
I've noticed isn't really with svn or rpmforge, but if you use viewvc
and have the EPEL repository enabled, yum will pick the epel viewvc
package and it's configuration is different from the rpmforge version.
For the people who have no idea what this is about: 'yum' is the
software package manager for the Centos linux distribution, EPEL is a
third-party package repository that tries not to modify packages
included in the distribution, and rpmforge is a repository that tries to
provide newer versions of base packages or versions with more features,
as well as additional programs. And yum is fairly easily confused when
3rd party repositories offer conflicting versions. My experience has
been that the rpmforge packages are well maintained, but you have to be
careful not to let yum pull in more than you need from there. If you
don't know how to do that, you can always download the individual rpms
and install manually.
Received on 2010-11-15 16:56:25 CET