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

Re: RHEL4 x86_64 issues with 'SASL' and difficulty installing i386 version on RHEL4 x86_64.

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Fri, 10 Jul 2009 19:07:31 -0400

On Fri, Jul 10, 2009 at 9:06 AM, Nico Kadel-Garcia<nkadel_at_gmail.com> wrote:
> On Fri, Jul 10, 2009 at 7:42 AM, Nico Kadel-Garcia<nkadel_at_gmail.com> wrote:
>> On Fri, Jul 10, 2009 at 5:46 AM, Radomir
>> Zoltowski<radomir.zoltowski_at_s3group.com> wrote:
>>> Is there a reason for not using CollabNet x86_64 RPMs? See here:
>>> http://www.open.collab.net/downloads/subversion/redhat.html
>>
>> Besides having to register for it, which I've always hated?
>>
>>> If you install i386 onto x86_64 machine, you need to provide all
>>> dependencies tree for i386 arch, too, which is usually quite entertaining
>>> task.
>>>
>>> R.
>>
>> See my notes below. The only tricky dependency was grabbing the
>> apr-util dependency. *BUT*, if you say "yum install subversion" (since
>> I use yum, which has vastly superior package management to RHEL's
>> up2date tool and works well with RPMforge and mock and EPEL), goes
>> ahead and installs the ancient subversion-1.1.x-foo.x86_64 version as
>> well as the contemporary subversion-1.6.3-bar.i386 version, which
>> seriously screws up the installation by replacing /usr/bin/svn.
>>
>> I'll take a shot at the collabnet RPM's, but I expect the same problem.
>
> Well, *that* was interesting. Collabnet does publish RPM's, as you
> suggest, but with their entirely personal and unique layout. They dump
> a bunch of material in interesting places, starting with a client in
> /opt, a server that puts a bunch of debris in /etc/opt/, and other
> vagaries. Comprehensible, but it would take thought to merge into our
> existing infrastructure. I need to think about its use carefully.
>
> Their x86_64 svn, however, does work correctly for the 'svn help'
> command. So I need to think about it: it's not just a drop in
> replacement, and either needs a bunch of symlinks created, or a "PATH"
> and "MANPATH" dropped into /etc/profile.d/collabnetsvn.sh to help out.
>

So, I tested the Collabnet version. It works just fine: Unfortunately,
I'm not in a position where I can switch the environment wholesale,
and only have the issue in x86_64 on RHEL 4, darn it. And re-arranging
a bunch of people's PATH and MANPATH is begging for pain in this
environment. I have to think about whether, and how, to integrate
this.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2370583

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-11 01:08:33 CEST

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.