You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Max Bowsher <ma...@ukf.net> on 2005/01/21 23:31:28 UTC

Re: "make install-swig-{pl,py}" implies "make install" for somelibraries (Issue 2126)

Greg Hudson wrote:
> On Fri, 2005-01-21 at 15:02, Shlomi Fish wrote:
>> 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.
>
> So, you're talking about an installation where there are Subversion
> modules in the system perl area, owned by root, linked against
> Subversion libraries in some other prefix owned by non-root?
>
> That sounds totally broken, and I don't think we should be trying to
> facilitate it.

There's lot's of permutations which can be useful.

e.g. I might have an /opt which I (for convenience) can install into as
myself, but need to become root to touch the perl install under /usr.


But far more persuasive for me is that flexibility has been sacrificed,
*and* potentially unexpected additional installation may occur, just to save
people from needing to type "make install install-foo".

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org