Before it was not possible to specify conflicting packages in recipes

using the debianize class.

Now the conflicting packages can be defined using the DEBIAN_CONFLICTS

variable in the recipe. This is especially useful in dpkg-raw recipes

that should conflict with each other.

Signed-off-by: Benjamin Schilling <schilling.benjamin@siemens.com>

---

meta/classes/debianize.bbclass | 3 +++

1 file changed, 3 insertions(+)

diff --git a/meta/classes/debianize.bbclass b/meta/classes/debianize.bbclass

index dad1cb4..4486778 100644

--- a/meta/classes/debianize.bbclass

+++ b/meta/classes/debianize.bbclass

@@ -1,5 +1,6 @@

# This software is a part of ISAR.

# SPDX-License-Identifier: MIT

@@ -7,6 +8,7 @@ CHANGELOG_V ??= "${PV}"

DPKG_ARCH ??= "any"

DEBIAN_BUILD_DEPENDS ??= ""

DEBIAN_DEPENDS ??= ""

+DEBIAN_CONFLICTS ??= ""

DESCRIPTION ??= "must not be empty"

MAINTAINER ??= "Unknown maintainer unknown@example.com"

@@ -63,6 +65,7 @@ Build-Depends: debhelper (>= ${compat}), ${DEBIAN_BUILD_DEPENDS}

Package: ${PN}

Architecture: ${DPKG_ARCH}

Depends: ${DEBIAN_DEPENDS}

+Conflicts: ${DEBIAN_CONFLICTS}

Description: ${DESCRIPTION}

EOF

}

2.20.1