public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schilling, Benjamin" <schilling.benjamin@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "henning.schild@siemens.com" <henning.schild@siemens.com>
Subject: [PATCH] meta: Add Debian package conflicts in debianize class
Date: Tue, 27 Jul 2021 13:54:12 +0000	[thread overview]
Message-ID: <AM9PR10MB4824A6E6B0A4B2FFE88FF32688E99@AM9PR10MB4824.EURPRD10.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

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.
# Copyright (C) 2017-2019 Siemens AG
+# Copyright (C) 2021 Siemens Mobility GmbH
#
# 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<mailto: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


[-- Attachment #2: Type: text/html, Size: 5329 bytes --]

             reply	other threads:[~2021-07-28  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 13:54 Schilling, Benjamin [this message]
2021-07-27 17:41 ` Henning Schild
2021-08-18  9:33 ` Anton Mikanovich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM9PR10MB4824A6E6B0A4B2FFE88FF32688E99@AM9PR10MB4824.EURPRD10.PROD.OUTLOOK.COM \
    --to=schilling.benjamin@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox