Hi Frode,
Last Thursday, during the OVN IRC meeting, you brought up the topic of
how to better handle the OVS submodule within OVN. As I recall, the
issue was that in Ubuntu, you can't download an arbitrary commit of OVS
strictly for compiling against OVN. You instead need to use the
installed OVS package on the system. In the meeting we focused on trying
to come up with policies to ensure that the submodule points to a
release branch of OVS.
However, Ilya brought up an alternate idea today. Currently, the release
tarball of OVN in github is strictly the OVN code with no submodule. If
there were a way to make the source tarball also include the OVS
submodule, then it should be enough to get the OVN source tarball and
compile it on its own. There would be no need to care about the version
of OVS installed on the system.
Would this solve the issue you are facing? If so, then we can focus on
coming up with an alternate method of creating source tarballs instead
of using the tag in github directly.
Thanks,
Mark Michelson
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
