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

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

From: Jens Seidel <jensseidel_at_users.sourceforge.net>
Date: Fri, 3 Oct 2008 14:15:09 +0200

On Thu, Oct 02, 2008 at 09:28:02PM -0600, Jeremy Whitlock wrote:
> New Make Targets
> -------------------------
> ctypes-python: This target will build the ctypes-python bindings.
> check-ctypes-python: This target will run the test suite for the
> ctypes-python bindings.
> install-ctypes-python: This target will install the ctypes-python
> bindings into the same location that Subversion is installed using
> Python conventions for the location of the Python packages.
> clean-ctypes-python: This target will clean up all build artifacts
> related to building the ctypes-python bindings.
>
> (The ctypes-python bindings can also be cleaned using the 'clean' and
> 'extraclean' make targets.)
 
> While the ctypes-python bindings are now integrated into the
> Subversion build process, there is still some work to be done. As it
> stands now, to build, test and install the ctypes-python bindings, you
> first have to install Subversion with 'make install'. We are
> currently working on updating the ctypes-python installer to allow for
> building and testing against the locally built Subversion instead of
> requiring an install of Subversion.

PS: There exist also similar errors in Subversions build system. See
e.g. http://svn.haxx.se/dev/archive-2008-08/0876.shtml. Nobody is
interested in a fix (I asked already twice) so it will not be fixed ...

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".

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.

Jens

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-03 14:29:12 CEST

This is an archived mail posted to the Subversion Dev mailing list.