mir/openvswitch
2
0
Fork 0
mirror of https://github.com/openvswitch/ovs synced 2025-10-15 14:17:18 +00:00
Code Issues Releases Wiki Activity
Files
429ebf217bd72fc28de6816bbbfeaf9ce006ecd9
openvswitch/debian/openvswitch-switch.install

13 lines
318 B
Plaintext
Raw Normal View History

debian: Modernize use of dh_install. Originally I intended this as just a cleanup, but as a side effect it also installs some files from the install tree in debian/tmp instead of from _debian. This should avoid a reported problem in which ovs-bugtool was being created in the source directory instead of the build directory (I still don't see why this happened). Reported-by: Sébastien RICCIO <sr@swisscenter.com> Tested-by: Sébastien RICCIO <sr@swisscenter.com> Acked-by: Simon Horman <horms@verge.net.au> CC: Simon Horman <horms@verge.net.au>
2011-07-26 09:22:45 -07:00
usr/bin/ovs-dpctl
usr/bin/ovs-pcap
usr/bin/ovs-tcpundump
usr/bin/ovs-vlan-test
usr/bin/ovs-vsctl
debian: Move OVSDB schema and ovsdb-tool to openvswitch-switch. ovs-vswitchd in the openvswitch-switch package is tightly coupled to its database schema. During development, it's possible to change the schema without changing the Open vSwitch version number, which makes it possible for the openvswitch-switch and openvswitch-common packages to get out of sync: openvswitch-switch requires the same version of openvswitch-common, but if the version number doesn't get updated that has no effect. Actually putting the schema and ovs-vswitchd (its primary user) in the same package prevents them from getting out-of-sync. This commit also moves ovsdb-tool because that program often works directly with OVSDB schemas and so there's not much point having it around without a schema to work with.
2011-07-26 09:46:38 -07:00
usr/bin/ovsdb-tool
debian: Modernize use of dh_install. Originally I intended this as just a cleanup, but as a side effect it also installs some files from the install tree in debian/tmp instead of from _debian. This should avoid a reported problem in which ovs-bugtool was being created in the source directory instead of the build directory (I still don't see why this happened). Reported-by: Sébastien RICCIO <sr@swisscenter.com> Tested-by: Sébastien RICCIO <sr@swisscenter.com> Acked-by: Simon Horman <horms@verge.net.au> CC: Simon Horman <horms@verge.net.au>
2011-07-26 09:22:45 -07:00
usr/sbin/ovs-vswitchd
usr/sbin/ovsdb-server
usr/share/openvswitch/scripts/ovs-ctl
usr/share/openvswitch/scripts/ovs-lib.sh
usr/share/openvswitch/scripts/ovs-save
debian: Move OVSDB schema and ovsdb-tool to openvswitch-switch. ovs-vswitchd in the openvswitch-switch package is tightly coupled to its database schema. During development, it's possible to change the schema without changing the Open vSwitch version number, which makes it possible for the openvswitch-switch and openvswitch-common packages to get out of sync: openvswitch-switch requires the same version of openvswitch-common, but if the version number doesn't get updated that has no effect. Actually putting the schema and ovs-vswitchd (its primary user) in the same package prevents them from getting out-of-sync. This commit also moves ovsdb-tool because that program often works directly with OVSDB schemas and so there's not much point having it around without a schema to work with.
2011-07-26 09:46:38 -07:00
usr/share/openvswitch/vswitch.ovsschema
Reference in New Issue Copy Permalink