[ovs-dev] Bug#826780: Bug#826780: Please package OVS >= 2.6.0.dev1

Russell Bryant russell at ovn.org
Fri Jun 10 01:33:03 UTC 2016


On Thu, Jun 9, 2016 at 11:50 AM, Terry Wilson <twilson at redhat.com> wrote:

> On Thu, Jun 9, 2016 at 3:07 AM, Russell Bryant <russell at ovn.org> wrote:
> > The real solution to making this less awkward would be to split the
> Python
> > library out of the OVS git tree so that it can be released independently
> of
> > OVS itself.  That way a proper verison could be released that includes
> > Python 3 support.
>
> This would be very nice. There are some challenges to overcome. The
> testing infrastructure between the Python and C implementations is
> shared. Out of tree it becomes more a bit more difficult to make sure
> that they stay in sync both feature and compatibility-wise. My gut
> feeling is that it would still be worth the work, though. There's no
> good reason for releases of the Python library to be tied OVS
> releases.


The next step in turning this into a real proposal would be to prototype
the split to show what the two repos would look like after the split.  It
should also document the impact on developers who need to change both, as
well as people working on just ovs (as the build system uses the python
lib).

To be clear, even though I think this is the "right" thing to do, I don't
expect I will do the work any time soon.
-- 
Russell Bryant



More information about the dev mailing list