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

Re: The RIGHT way to upgrade Subversion on FC2 = ??

From: Kenneth Porter <shiva_at_sewingwitch.com>
Date: 2006-08-23 02:43:11 CEST

--On Tuesday, August 22, 2006 8:34 PM -0400 Eric <spamsink@scoot.netis.com>

> So, what is the consensus of the BEST way to get subversion upgraded
> correctly on FC2?

I haven't upgraded in awhile, but my approach is to go to the Rawhide SRPM
directory and grab the latest SRPM available for all Red Hat and Fedora
systems. Rawhide generally tracks the upstream HEAD.

Once you have the SRPM, repackage it. There's a page in the Fedora wiki on
how to repackage a source RPM into a binary RPM. Because you do it on FC2,
it will use the libraries you have installed. You won't have any
dependencies on libraries only available in later distributions.

It's still possible the source package will have dependencies on libraries
not available with FC2. If so, you may have to get those libraries from
Rawhide and repackage them as well. With any luck this won't drive you into
a new version of glibc or a new kernel, or SELinux. (I got stuck trying to
upgrade Mailman due to an indirect dependency on SELinux.)

It's important to remember that building from an SRPM *is* building from
source. An SRPM is just the original source wrapped with distro-specific
patches and a meta-makefile (the spec file) that builds a package in a way
that's compatible with the distro's filesystem layout.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 23 02:44:26 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.