public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: srinuvasan.a@siemens.com, isar-users@googlegroups.com
Cc: felix.moessbauer@siemens.com
Subject: Re: [PATCH] meta/classes/debianize: Add copyright file to debian folder
Date: Thu, 29 Feb 2024 20:14:41 +0100	[thread overview]
Message-ID: <c922453e7c050556917b398ada83ab8032cda5ec.camel@siemens.com> (raw)
In-Reply-To: <20240228072206.3556467-1-srinuvasan.a@siemens.com>

Hi,

On Wed, 2024-02-28 at 12:52 +0530, srinuvasan.a via isar-users wrote:
> From: Srinuvasan A <srinuvasan.a@siemens.com>
> 
> In downstream layer we uses copyright files for most of the packages,
> this is very important for our OSS clearing.
> 
> User can add the copyright to the required recipe, then the generated
> packages from the recipes contains the debian/copyright file.
> 
> Added example copyright file in example-raw recipe.
> 
> Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
> ---
>  .../recipes-app/example-raw/example-raw_0.3.bb    |  3 ++-
>  .../example-raw/files/default-copyright.tmpl      | 15 +++++++++++++++
>  meta/classes/debianize.bbclass                    |  4 ++++
>  3 files changed, 21 insertions(+), 1 deletion(-)
>  create mode 100644 meta-isar/recipes-app/example-raw/files/default-copyright.tmpl
> 
> diff --git a/meta-isar/recipes-app/example-raw/example-raw_0.3.bb b/meta-isar/recipes-app/example-raw/example-raw_0.3.bb
> index ffa14340..b4dfaa4d 100644
> --- a/meta-isar/recipes-app/example-raw/example-raw_0.3.bb
> +++ b/meta-isar/recipes-app/example-raw/example-raw_0.3.bb
> @@ -9,7 +9,8 @@ DEBIAN_DEPENDS = "adduser, apt (>= 0.4.2)"
>  
>  SRC_URI = "file://README \
>  	   file://postinst \
> -	   file://rules"
> +	   file://rules \
> +	   file://default-copyright.tmpl"
>  
>  inherit dpkg-raw
>  
> diff --git a/meta-isar/recipes-app/example-raw/files/default-copyright.tmpl b/meta-isar/recipes-app/example-raw/files/default-copyright.tmpl
> new file mode 100644
> index 00000000..9c04255a
> --- /dev/null
> +++ b/meta-isar/recipes-app/example-raw/files/default-copyright.tmpl
> @@ -0,0 +1,15 @@
> +Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> +Upstream-Name: ${PN}
> +Upstream-Contact: Mentor Embedded <embedded_support@mentor.com>
> +Source: https://github.com/MentorEmbedded/industrial-core

Mentor or Siemens? And how did you make sure that "we" really hold the
copyright?

> +
> +Files: *
> +Copyright: 2022, Siemens
> +License: Siemens

Wrong year...

> + .
> + This material contains trade secrets or otherwise confidential information
> + owned by Siemens Industry Software Inc.or its affiliates (collectively,
> + "Siemens"), or its licensors. Access to and use of this information is strictly
> + limited as set forth in the Customer's applicable agreements with Siemens.
> + .
> + Unpublished work. Copyright 2023 Siemens

Nope. Now its published and in addition: wrong year...

> diff --git a/meta/classes/debianize.bbclass b/meta/classes/debianize.bbclass
> index 7de98673..5b9cd9dc 100644
> --- a/meta/classes/debianize.bbclass
> +++ b/meta/classes/debianize.bbclass
> @@ -112,6 +112,10 @@ deb_debianize() {
>  	else
>  		deb_create_rules
>  	fi
> +	# Add the copyright if unpacked sources does not contain copyright file
> +	if [ ! -f ${S}/debian/copyright.tmpl ] && [ -f ${WORKDIR}/default-copyright.tmpl ]; then
> +		install -v -m 644 ${WORKDIR}/default-copyright.tmpl ${S}/debian/copyright
> +	fi

This magic should be documented somewhere - after we agreed that this
is really the best way to add such a copyright file.

>  	# prepend a changelog-entry unless an existing changelog file already
>  	# contains an entry with CHANGELOG_V
>  	deb_add_changelog
> -- 
> 2.34.1


  parent reply	other threads:[~2024-02-29 19:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28  7:22 srinuvasan.a
2024-02-29  1:10 ` Jan Kiszka
2024-02-29  5:02   ` srinu
2024-03-01  7:36     ` Jan Kiszka
2024-03-07 14:48       ` [PATCH v2] " srinuvasan.a
2024-03-08  7:15         ` Jan Kiszka
2024-03-08  7:18           ` srinu
2024-03-08 14:26           ` [PATCH v3] " srinuvasan.a
2024-03-08 14:37             ` Jan Kiszka
2024-03-11  6:22               ` [PATCH v4 1/2] " srinuvasan.a
2024-03-11  6:22                 ` [PATCH v4 2/2] doc/user_manual: add a section for debianize class srinuvasan.a
2024-03-12 16:10                   ` srinu
2024-03-12 16:36                   ` Jan Kiszka
2024-03-13  5:57                     ` [PATCH v5 " srinuvasan.a
2024-03-13  8:38                       ` Florian Bezdeka
2024-03-13  9:44                         ` [PATCH v6 " srinuvasan.a
2024-03-15 12:56                           ` Uladzimir Bely
2024-03-12 16:34                 ` [PATCH v4 1/2] meta/classes/debianize: Add copyright file to debian folder Jan Kiszka
2024-03-15 12:55                 ` Uladzimir Bely
2024-02-29 19:14 ` Florian Bezdeka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-28  5:44 [PATCH] " Srinuvasan A
2024-02-29  8:10 ` MOESSBAUER, Felix
2024-02-29 19:04 ` Florian Bezdeka
2024-03-14  9:12 ` Cedric Hombourger
2024-03-14 12:09   ` srinu

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=c922453e7c050556917b398ada83ab8032cda5ec.camel@siemens.com \
    --to=florian.bezdeka@siemens.com \
    --cc=felix.moessbauer@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