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

svnmucc installation bug in Subversion 1.8.0

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Thu, 20 Jun 2013 22:36:19 -0400

I'm trying to build up a subversion-1.8.0 SRPM toolkit, and have
noticed a little "svnucc" deployment bug.

Specifically, the Makefile winds up saying this:

# Compatibility symlink.
# This runs after the target of the same name in build-outputs.mk.
  $(MKDIR) $(DESTDIR)$(bindir); \
  test -n "$$SVN_SVNMUCC_IS_SVNSYITF" && \
  ln -sf svnmucc$(EXEEXT) $(DESTDIR)$(bindir)/svnsyitf$(EXEEXT); \
  if test "$(DESTDIR)$(bindir)" != "$(DESTDIR)$(toolsdir)"; then \
    ln -sf $(DESTDIR)$(bindir)/svnmucc$(EXEEXT)
$(DESTDIR)$(toolsdir)/svnmucc$(EXEEXT); \

Unfortunately, when building RPM's "DESTDIR" is the location of the
RPM "BUILDROOT" location, not the atual deployment location. So it
needs to be:

    ln -sf $(bindir)/svnmucc$(EXEEXT) $(DESTDIR)$(toolsdir)/svnmucc$(EXEEXT); \

So can I safely assume that I just need to patch that for RPM building?
Received on 2013-06-21 04:36:59 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.