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

Re: svnmucc installation bug in Subversion 1.8.0

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Fri, 21 Jun 2013 09:45:35 +0100

Nico Kadel-Garcia <nkadel_at_gmail.com> writes:

> # Compatibility symlink.
> # This runs after the target of the same name in build-outputs.mk.
> INSTALL_EXTRA_TOOLS=\
> $(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); \
> fi
>
>
> 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?

That should work. I fixed Makefile.in in r1495329.

Does your binary package include /usr/bin/svn-tools?

-- 
Philip Martin | Subversion Committer
WANdisco | Non-Stop Data
www.wandisco.com
Received on 2013-06-21 10:46:28 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.