Opened 18 years ago

Closed 18 years ago

#1797 closed task (fixed)

Subversion-1.3.1

Reported by: Randy McMurchy Owned by: Randy McMurchy
Priority: normal Milestone: 6.2.0
Component: BOOK Version: SVN
Severity: normal Keywords: Subversion
Cc:

Description

Version increment to 1.3.0

Change History (15)

comment:1 by Chris Staub, 18 years ago

One change that would need to be made to the instructions - subversion 1.2.3 will use libxml2 if it's found...however 1.3.0 will use expat (either its own or found on the system) unless you specify "--with-libxml2" on the configure line.

comment:2 by Chris Staub, 18 years ago

Found something strange...it seems subversion 1.3.0 won't use libxml2 at all (even if you specify --with-libxml2 on the configure command) unless you also have expat installed on your system. Can someone verify this behavior, and make sure it's not just due to me doing something dumb?

comment:3 by bdubbs@…, 18 years ago

You don't specify what optional packages you have installed. What options are you passing to configure?

On a related note, did anyone else note that subversion installs two files in /usr/build: apr_rules.mk and libtool ?

This is a non-standard directory in /usr.

comment:4 by dnicholson@…, 18 years ago

For the two files in /usr/build: I noted this some time ago on blfs-dev, but now it's gone by the wayside and I'm not going back through the mailing lists right now. It has to do with the apr runtime being installed if you don't have apache. Check out the patch that's in apache for FHS compliance http://www.linuxfromscratch.org/patches/blfs/svn/httpd-2.2.0-config-1.patch .

Something similar should be crafted for svn. I think last time I built svn, I did some sed'ing, but I can't remember. If I have a patch, I'll report back. We need to decide where those go, too, or suppress their installation.

comment:5 by Chris Staub, 18 years ago

I used "./configure --prefix=/usr --with-libxml2 --with-ssl". I did this right after installing libxml2, and subversion configure still said it was using the expat in it's own source dir for xml parsing. I installed expat, then ran configure on subversion again, and this time it reported it would use libxml2. However, ldd on /usr/bin/svn reports that it's linked against both libxml2 and expat. I just checked, and it seems that apr uses expat, and neon uses libxml2.

comment:6 by Chris Staub, 18 years ago

Slight change...neon *can* use libxml2...it's not required. There is already another ticket open about the inaccurate description of libxml2 as "required".

comment:7 by dnicholson@…, 18 years ago

I just built neon by itself the other day (can't remember the reason why). I think in the README, it states that it can use either libxml2 or expat. But that was the released version 0.24.7. I don't know what's bundled in subversion.

comment:8 by Chris Staub, 18 years ago

Subversion 1.3.0 bundles neon 0.25.4, which can also use either expat or libxml2.

comment:9 by Chris Staub, 18 years ago

Just wanted to verify the issue with subversion and libxml2. I have a base CLFS system (unlike LFS, no Berkeley DB) + GPM + dhcpcd + libxml2 - that's it. I configured subversion with "./configure --prefix=/usr --with-libxml2" and configure reports that's it's still using subversion's own internal expat libs. And I just checked again and it seems subversion 1.2.3 does the same thing. From looking at the configure script it seems that if expat isn't found on the system (even if libxml2 is) the main svn configure script passes --with-expat=[sourcedir]/apr-util/xml/expat to the neon configure script. If expat is found on the system, this isn't done so neon is able to use libxml2.

comment:10 by martyman99999@…, 18 years ago

Built and installed okay. Careful with /usr/share/doc/subversion-1.3.0, lots of files got installed world no access and directories without execute access.

comment:11 by Randy McMurchy, 18 years ago

Keywords: Subversion added
Milestone: future6.2
Owner: changed from blfs-book@… to Randy McMurchy
Type: defecttask

comment:12 by Randy McMurchy, 18 years ago

Status: newassigned

comment:13 by Randy McMurchy, 18 years ago

Summary: Subversion-1.3.0Subversion-1.3.1

Version increment to 1.3.1

Going to build and test to see if the BDB issue is gone.

Also will address the bastard files installed if you don't have system-installed Neon and the libxml2 dependency.

comment:14 by Randy McMurchy, 18 years ago

I should correct the reference to Neon above and say it is the Apache APR stuff that gets installed in /usr/something. Archaic sent me a message that provides a switch on configure that supposedly fixes this.

I cannot test it, as all system I have available have Apache on it. I will include it in the update, however, as I trust Archaic on this one.

The libxml thing is a no-brainer, the dependency simply moves to optional.

Also notated in this bug is the Neon version which can be used. Subversion will now use all system-installed versions up to 0.25.5 but not the 0.26.x series.

Everything mentioned will be addressed in the update.

comment:15 by Randy McMurchy, 18 years ago

Resolution: fixed
Status: assignedclosed

Updated BLFS to Subversion-1.3.1

Added a flag to configure to suppress building the BDB back-end libraries and added notes to the server and client pages warning about the BDB issue.

Note: See TracTickets for help on using tickets.