On Mon, Dec 12, 2011 at 12:26 AM, Simon Horman <ho...@verge.net.au> wrote: > On Mon, Dec 12, 2011 at 08:00:25AM +0000, Ben Hutchings wrote: >> Since a version of Open vSwitch has been accepted for inclusion in >> mainline Linux 3.3, perhaps it could be included in Debian kernel >> packages starting with Linux 3.2 and then this binary package could be >> removed. However I don't know whether the mainline version is fully- >> featured. > > Hi Ben, > > the mainline version is fully featured and I envisage that the > openvswitch-datapath package can be removed from the archive at some point. > I would value your input on how that might be best achieved.
The upstream version is actually not quite fully featured. There is currently no support for tunneling upstream because we wanted to spent some time thinking about the interfaces before finalizing them. We did quite a bit of this for the main components of Open vSwitch and thought it was better to get that upstream first since it was ready and more or less independent. The other piece that is not upstream is support for bridge compatibility (although the bulk of this is in a separate module, it requires some hooks into the main one). We hope that this continues to become less necessary over time and aren't planning to propose that for upstream Linux. As Ben mentioned, the best solution for now to just upload OVS 1.3. > As for the compile problem below, this is intended by upstream, > though perhaps isn't appropriate for Debian. I'll take guidance > on that issue from upstream. The #error message is only intended to make the source of the problem obvious to users who are compiling the module out-of-tree. Compilation would have failed anyways due to changes in the kernel headers. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
