subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nico Kadel-Garcia <>
Subject Re: mod_dontdothat RPM building problems with subversion-1.7.6
Date Fri, 17 Aug 2012 02:38:54 GMT
On Thu, Aug 16, 2012 at 6:55 PM, Daniel Shahaf <> wrote:
> Nico Kadel-Garcia wrote on Thu, Aug 16, 2012 at 01:31:11 -0400:
>> On Wed, Aug 15, 2012 at 7:52 AM, Philip Martin <> wrote:
>> > I'm happy to announce the release of Apache Subversion 1.7.6.
>> > Please choose the mirror closest to you by visiting:
>> >
>> >
>> Cool. I'm poking at getting a 1.7.6 SRPM set up for it. I am noticing an issue.
> In the future you may consider testing the packaging when the tarballs
> are posted for developer testing, rather than only after their public
> release.  (at which point they can no longer be pulled)

Sorry, Daniel: I was busy on one contract until July 31 and just
started a new one Monday.

>> * Make installable from the Makefile. The easiest
>> way to do it is to move it to from "tools" to "subversion", parallel
>> to subverson/mod_dav_svn, and as a loadable httpd module, it requires
>> special attention.
>> * Make the other Subversion tools installable. It should be
>> straightforward to make the other contents of the "tools" directory
>> compiled and instlalled into the 'toolsdir', typically
>> /usr/local/bin/svn-tools, defined in the It's not
>> currently used in subverson-1.7.x, but is used in the trunk for the
>> "svnmucc" tools.
> Are you aware of 'make install-tools'?

I looked in the Makefile and didn't see it, unlike 'install-man",
"install-swig-rb", etc. But sure enough, it works. Gotta love
sophisticated and impliciit components of Makefiles. Thanks for the

Is there some reason it's not included in the default "install" list of targets?

> If you want to add targets to install individual tools, too, I imagine
> we would welcome a patch for this (but I won't have time to handle it
> myself).  See the 1.7.5->1.7.6 diff for most of the files you'll need to
> touch (makefile.ezt and co).

That's potentially useful, but doens't fix the problem where the built
components are in "tools" are

View raw message