public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>, isar-users@googlegroups.com
Cc: "Dalamagkidis, Konstantinos" <konstantinos.dalamagkidis@siemens.com>
Subject: Re: [PATCH 2/5] debianize: move variable defaults to the class that needs them
Date: Wed, 6 Nov 2019 17:20:10 +0100	[thread overview]
Message-ID: <822ff1c8-77c7-3835-8722-f8b07f026c23@siemens.com> (raw)
In-Reply-To: <20191029164424.14681-3-henning.schild@siemens.com>

On 29.10.19 17:44, Henning Schild wrote:
> From: Henning Schild <henning.schild@siemens.com>
> 
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
>  meta/classes/debianize.bbclass | 3 +++
>  meta/classes/dpkg-raw.bbclass  | 3 ---
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/meta/classes/debianize.bbclass b/meta/classes/debianize.bbclass
> index 33ab4f7..fb9c234 100644
> --- a/meta/classes/debianize.bbclass
> +++ b/meta/classes/debianize.bbclass
> @@ -5,6 +5,9 @@
>  
>  CHANGELOG_V ?= "${PV}"
>  DPKG_ARCH ??= "any"
> +DEBIAN_DEPENDS ?= ""
> +DESCRIPTION ?= "must not be empty"

Then, shouldn't we rather leave it empty here and fail if it remains so?

> +MAINTAINER ?= "Unknown maintainer <unknown@example.com>"
>  
>  deb_add_changelog() {
>  	timestamp=$(find ${S}/ -type f -not -path "${S}/debian/*" -printf "%T@\n"|sort -n -r|head -n 1)
> diff --git a/meta/classes/dpkg-raw.bbclass b/meta/classes/dpkg-raw.bbclass
> index 3f19f8e..8c01a46 100644
> --- a/meta/classes/dpkg-raw.bbclass
> +++ b/meta/classes/dpkg-raw.bbclass
> @@ -5,9 +5,6 @@
>  
>  inherit dpkg
>  
> -DEBIAN_DEPENDS ?= ""
> -MAINTAINER ?= "Unknown maintainer <unknown@example.com>"
> -
>  D = "${S}"
>  
>  # Populate folder that will be picked up as package
> 

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2019-11-06 16:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 16:44 [PATCH 0/5] document debianize.bbclass Henning Schild
2019-10-29 16:44 ` [PATCH 1/5] debianize: only prepend changelog when our entry is not there Henning Schild
2019-10-29 16:44 ` [PATCH 2/5] debianize: move variable defaults to the class that needs them Henning Schild
2019-11-06 16:20   ` Jan Kiszka [this message]
2019-11-07 18:40     ` Henning Schild
2019-10-29 16:44 ` [PATCH 3/5] meta-isar/recipes-app: add debianize test package "samefile" Henning Schild
2019-10-29 16:44 ` [PATCH 4/5] doc: write something about "debianize" Henning Schild
2019-11-01  7:08   ` chombourger
2019-11-04 10:01     ` Henning Schild
2019-11-06 16:26   ` Jan Kiszka
2019-11-07 18:42     ` Henning Schild
2019-10-29 16:44 ` [PATCH 5/5] CI: add "samefile" to our example config and CI build Henning Schild

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=822ff1c8-77c7-3835-8722-f8b07f026c23@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=konstantinos.dalamagkidis@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