public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Cc: cedric.hombourger@siemens.com, Srinuvasan <srinuvasan.a@siemens.com>
Subject: Re: [PATCH] debianize: Introduce DEBIAN_PROVIDES and DEBIAN_REPLACES
Date: Fri, 16 Feb 2024 09:38:07 +0300	[thread overview]
Message-ID: <f18fc53cfa829274d9ab61d62e9bec7e63cc62ae.camel@ilbers.de> (raw)
In-Reply-To: <20240213125605.1964664-1-srinuvasan_a@mentor.com>

On Tue, 2024-02-13 at 18:26 +0530, Srinuvasan Arjunan wrote:
> From: Srinuvasan <srinuvasan.a@siemens.com>
> 
> Allow setting the Provides and Replaces field for auto generated
> control files,
> with this changes now user can configure the provides and replaces in
> the debian/control file.
> 
> Recipes can simply setting the Provides and Replaces field now by
> defining the
> DEBIAN_PROVIDES and DEBIAN_REPLACES variable.
> 
> Signed-off-by: Srinuvasan <srinuvasan.a@siemens.com>
> ---
>  meta/classes/debianize.bbclass | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/meta/classes/debianize.bbclass
> b/meta/classes/debianize.bbclass
> index 16f3638d..72afea88 100644
> --- a/meta/classes/debianize.bbclass
> +++ b/meta/classes/debianize.bbclass
> @@ -8,6 +8,8 @@ CHANGELOG_V ??= "${PV}"
>  DPKG_ARCH ??= "any"
>  DEBIAN_BUILD_DEPENDS ??= ""
>  DEBIAN_DEPENDS ??= ""
> +DEBIAN_PROVIDES ??= ""
> +DEBIAN_REPLACES ??= ""

This looks like considering my comment in the same patch from Cedric
Hombourger
(https://groups.google.com/g/isar-users/c/fpPkw0WxQno/m/CLIq3fo8BwAJ),
but this patch misses original modification of user_manual.md.

>  DEBIAN_CONFLICTS ??= ""
>  DEBIAN_MULTI_ARCH ??= "no"
>  DESCRIPTION ??= "must not be empty"
> @@ -77,6 +79,8 @@ Build-Depends: debhelper (>= ${compat}),
> ${DEBIAN_BUILD_DEPENDS}
>  Package: ${BPN}
>  Architecture: ${DPKG_ARCH}
>  Depends: ${DEBIAN_DEPENDS}
> +Provides: ${DEBIAN_PROVIDES}
> +Replaces: ${DEBIAN_REPLACES}
>  Conflicts: ${DEBIAN_CONFLICTS}
>  Multi-Arch: ${DEBIAN_MULTI_ARCH}
>  Description: ${DESCRIPTION}
> -- 
> 2.39.2
> 


  parent reply	other threads:[~2024-02-16  6:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 12:56 Srinuvasan Arjunan
2024-02-13 18:48 ` Florian Bezdeka
2024-02-16  6:38 ` Uladzimir Bely [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-28  9:41 [PATCH] debianize: introduce " srinuvasan.a
2024-03-04  6:08 ` srinu
2024-03-04 12:15   ` Uladzimir Bely
2024-03-06  7:20 ` Uladzimir Bely
2023-11-14 19:05 Cedric Hombourger
2023-11-16  7:07 ` 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=f18fc53cfa829274d9ab61d62e9bec7e63cc62ae.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=cedric.hombourger@siemens.com \
    --cc=isar-users@googlegroups.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