Re: ctypes-python bindings are now integrated into the Subversion build infrastructure

> I'm curious (and asked it already in the past): Why are there separate
> Makefile target such as install-ctypes-python? OK, currently it seems
> required until you have a fix for a locally built Subversion but
> shouldn't later the "install" target depend on "install-ctypes-python"
> by default?
>
> Please note that you do the same already for "clean".

Well, in my case I just followed convention. I'm sure this convention
is there for a reason but it is your right to ask.

> The current status is that the user has to read large Readme files and
> to remember really many Makefile targets, which need to be called in a
> special order. Why not build/install anything which is enabled and found
> by configure? If the user doesn't want ctypes-python bindings it should
> be either disabled by default or the user should select a
> --disable-ctypes-python flag of configure.

Maybe you should bring this up in a new thread, prepend the title with
[RFC] and ask your questions there. I'm sorry you feel we're not
listening.

-- 
Take care,
Jeremy Whitlock
http://www.thoughtspark.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org