public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "srinuvasan.a via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: cedric.hombourger@siemens.com,
	Srinuvasan Arjunan <srinuvasan.a@siemens.com>
Subject: [PATCH] debianize: introduce DEBIAN_BREAKS
Date: Wed,  8 Jan 2025 20:36:42 +0530	[thread overview]
Message-ID: <20250108150642.57626-1-srinuvasan.a@siemens.com> (raw)

From: Srinuvasan Arjunan <srinuvasan.a@siemens.com>

Allow setting the Breaks field for auto generated control files,
with this changes now user can configure the Breaks in the debian/control file.

Recipes can simply set the Breaks field now by defining the
DEBIAN_BREAKS variable.

Signed-off-by: Srinuvasan Arjunan <srinuvasan.a@siemens.com>
---
 doc/user_manual.md             | 1 +
 meta/classes/debianize.bbclass | 2 ++
 2 files changed, 3 insertions(+)

diff --git a/doc/user_manual.md b/doc/user_manual.md
index 706c74bf..7a35d8a4 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -958,6 +958,7 @@ Note that the package will be build using the whole debian package workflow, so
 Other (optional) customization variables include:
  - `DEBIAN_PROVIDES` - declare a virtual package to satisfy dependencies
  - `DEBIAN_REPLACES` - to replace a package with another
+ - `DEBIAN_BREAKS` - Packages which break other packages
 
 ### Prebuilt .deb packages from somewhere
 
diff --git a/meta/classes/debianize.bbclass b/meta/classes/debianize.bbclass
index 1d5fd83c..cf808eec 100644
--- a/meta/classes/debianize.bbclass
+++ b/meta/classes/debianize.bbclass
@@ -11,6 +11,7 @@ DEBIAN_DEPENDS ??= ""
 DEBIAN_PROVIDES ??= ""
 DEBIAN_REPLACES ??= ""
 DEBIAN_CONFLICTS ??= ""
+DEBIAN_BREAKS ??= ""
 DEBIAN_MULTI_ARCH ??= "no"
 DEBIAN_COMPAT ??= "10"
 DESCRIPTION ??= "must not be empty"
@@ -78,6 +79,7 @@ Architecture: ${DPKG_ARCH}
 Depends: ${DEBIAN_DEPENDS}
 Provides: ${DEBIAN_PROVIDES}
 Replaces: ${DEBIAN_REPLACES}
+Breaks: ${DEBIAN_BREAKS}
 Conflicts: ${DEBIAN_CONFLICTS}
 Multi-Arch: ${DEBIAN_MULTI_ARCH}
 Description: ${DESCRIPTION}
-- 
2.39.5

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20250108150642.57626-1-srinuvasan.a%40siemens.com.

             reply	other threads:[~2025-01-08 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 15:06 srinuvasan.a via isar-users [this message]
2025-01-16  7:02 ` Uladzimir Bely

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=20250108150642.57626-1-srinuvasan.a@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=srinuvasan.a@siemens.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