On Jan 21, 2005, at 2:02 PM, Shlomi Fish wrote:
> Check:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=2126
>
> For the bug report. I already wrote a patch to it, and a log message.
>
> The problem is that when typing make install-swig-pl or make
> install-swig-py,
> the make program also installs some of the Subversion libraries. This
> is
> problematic because installing the Perl bindings is usually done as
> root,
> which causes to install the Subversion libraries as root. However, it
> is
> highly possible these libraries should be installed as a regular user
> (under
> say a non-priviliged path) and not as root.
>
> It's also causes the install to be more time-consuming, but this is a
> more
> minor issue.
>
> Greg Hudson commented in the bug report that we should decide whether
> to
> enforce this policy for every "make install-foo" implies "make
> install-bar"
> situation. While possibly true, I cannot think of any other place
> where this
> bothers people as much as this case.
>
>
In my mind, there's a clear dependency between the 'install-swig-pl'
and 'install' targets. You cannot install functional bindings unless
core svn libraries are installed first.
By denying this dependency, I think we'd be making our build system
inconvenient for the majority of users; I think the majority of people
install *all* of subversion (binaries, libs, and bindings) as a single
user, and often all at once. It would be unfriendly for 'make
install-swig-pl' to throw an error about missing svn libraries (or
worse, silently installing non-functional bindings!)
Maybe a better compromise is to make a new target that *only* installs
bindings, and has no dependencies?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 21 21:19:49 2005