[Bug 428718] Review Request: pysvn - Python bindings for Subversion

bugzilla at redhat.com bugzilla at redhat.com
Tue Feb 26 18:30:14 UTC 2008


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: pysvn - Python bindings for Subversion


https://bugzilla.redhat.com/show_bug.cgi?id=428718


timothy.selivanow at virtualxistenz.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Review Request: python-svn -|Review Request: pysvn -
                   |Python bindings for         |Python bindings for
                   |Subversion                  |Subversion




------- Additional Comments From timothy.selivanow at virtualxistenz.com  2008-02-26 13:30 EST -------
So...I've been able to make all of the requested changes but one: pycxx dependency.

The others were easy, even over-sights on my part, but pysvn and pycxx are very
interwoven, in fact pycxx only exists for pysvn (same developer/maintainer, and
only went as far as making pycxx so he could get pysvn done).

If pycxx needs its own package (i.e. people would like to use it), then I'll
look at it.  As it is, pysvn pulls in the pycxx source and headers itself and
compiles pycxx itself, statically, for itself.  pycxx by itself does not have a
fully (Red Hat/Fedora) usable makefile and pysvn's needs tweaking for support,
and I'll have to learn a lot more about C++ and compiling C++ for use in a
shared library environment.

I know that in the past, syslog-ng 1.x had a dependency that was included so it
could build.  What is the policy now?

For now (http://koji.fedoraproject.org/koji/taskinfo?taskID=471353):
http://yum.virtualxistenz.com/pysvn/pysvn.spec
http://yum.virtualxistenz.com/pysvn/pysvn-1.5.2-6.f8.src.rpm (do I reset the
release version after the name changes?)

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




More information about the package-review mailing list