split into implementation and API endpoint packages

To better handle the case where firewall requires to parse the SDN
config and this package here would like to mount some vnet specific
firewall endpoints, without a split we got a cyclic dependency here,
and those are painful, especially on bootstrapping.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

1 files changed, 14 insertions, 1 deletions

diff --git a/debian/control b/debian/control
index 6c08fbf..687bbd7 100644
--- a/debian/control
+++ b/debian/control
@@ -26,5 +26,18 @@ Depends: libpve-common-perl (>= 5.0-45),
 Recommends: ifupdown2
 Suggests: frr-pythontools (>= 8.5.1~), dnsmasq,
 Description: Proxmox VE's SDN (Software Defined Network) stack
- This package contains the Software Defined Network (tech preview) for
+ This package contains the perl side of the Software Defined Network
+ implementation for Proxmox VE.
+
+Package: libpve-network-api-perl
+Architecture: all
+Depends: libpve-common-perl (>= 5.0-45),
+         pve-cluster (>= 8.0.9),
+         libpve-network-perl (= ${binary:Version}),
+         ${misc:Depends},
+         ${perl:Depends},
+Breaks: libpve-network-perl (<< 0.9.9~),
+Replaces: pve-cluster (<< 0.9.9~),
+Description: API endpoints for Proxmox VE's SDN stack
+ This package contains the API endpoints for the Software Defined Network of
  Proxmox VE.