On Sun, Oct 18, 2009 at 18:35, Maciej (Matchek) Blizinski <[email protected]> wrote: > I got pysvn-1.7.1 to build. It's in testing. > > For the package name conflict, I suggest the following: > > 1. Replacing the subversion-provided pysvn with pysvn.tigris.org, > preserving the both pkgname and catalog name. It will look like a > version bounce from 1.6.2 to 1.7.1. (justification: pysvn is the name > of the project, it's more specific than the generic notion of bindings > between subversion and Python.) > > 2. Creating a new package with subversion-provided Python bindings to > subversion_py CSWsubversion-py, or something similar. It will be clear > that it belongs to packages such as CSWsubversion and > CSWsubversion-devel. For instance: http://dpaste.com/108954/ (I know > it breaks the py_* rule, but it's a good thing: it's not a very useful > module, there's no harm in people not seeing it often when looking for > Python subversion bindings) > > Thoughts?
would this mean existing dependencies would work out if one replaces the contents with something else? rupert _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
