summaryrefslogtreecommitdiffstats
path: root/recipes-networking/openvswitch/files/openvswitch-add-target-python-handling.patch
Commit message (Collapse)AuthorAgeFilesLines
* openvswitch: uprev to 2.6.1Mark Asselstine2017-01-121-136/+0
| | | | | | | | | | | | | | | Pick up the latest features, including compatability with the latest DPDK as well as bug fixes. The patches for TARGET_PYTHON and TARGET_PERL can be dropped as configure now lets us pass these in the env (which we set). The systemd service files have been shuffled some upstream and we make adjustments in the recipe to accomodate these. The sysvinit scripts remain functional as they are. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* openvswitch: uprev to v2.1.2Bruce Ashfield2014-05-141-58/+45
| | | | | | | Updating to the latest OVS 2.x. Only minor patch refreshes required, and no regressions were found during sanity testing. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* openvswitch: add split between host and target python and perl pathsMark Asselstine2013-06-271-0/+149
Openvswitch is built with the assumption that the PYTHON and PERL variables are common between the host and target. This can result in improper paths used for script substitutions which in turn causes scripts which will fail to run on the target and the generated packages to have improper REQUIRES, making them impossible to install. These are usually not an issue since python and perl are found in the same location on the host and target, but there is no guarantee of this so the possibility of failure exists. By explicitly defining the location of the python and perl on the target we can avoid these assumptions and possibility of failure. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>