From: srinu <srinuvasan.a@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta/classes/debianize: Add copyright file to debian folder
Date: Thu, 14 Mar 2024 05:09:06 -0700 (PDT) [thread overview]
Message-ID: <13f40102-3123-4d54-a5cc-f94e308b0c26n@googlegroups.com> (raw)
In-Reply-To: <8576cd93-8ec2-468e-b9f4-0783ffa8486dn@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 4390 bytes --]
On Thursday, March 14, 2024 at 2:42:24 PM UTC+5:30 Cedric Hombourger wrote:
Le mercredi 28 février 2024 à 06:45:03 UTC+1, Srinuvasan A a écrit :
From: Srinuvasan A <srinuv...@mentor.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 <srinuv...@mentor.com>
please use your @siemens.com address moving forward
Yes after got the special User ID and password am using the siemens
account, in this thread itself i changed to siemens ID.
please explicitly cc the main contributors of the "Isar extensions" from
our downstream project when upstreaming them (especially when you change
them)
they will get a chance to review (e.g. I am not subscribed to isar-users
and only check the archives once a week or so)
Sure, i will add the respective persons for the review.
---
.../recipes-app/example-raw/example-raw_0.3.bb | 3 ++-
.../example-raw/files/default-copyright | 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
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..35f4b3d9 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"
the license helper in our downstream project was introduced to make it a
one-liner for dpkg-raw packages to get a debian/copyright especially when
they use "standard" licenses
IMO, debianize.bbclass should check ${LICENSE} if it matches a well-known
OSS license, add a default debian/copyright file (matching that license)
We should add default copyright texts for MIT, Apache-2, GPLv2, GPLv2+,
GPLv3, etc.
We should use templates (.tmpl) for all OSS licenses we provide a generic
debian/copyright file for
Let me check this one
inherit dpkg-raw
diff --git a/meta-isar/recipes-app/example-raw/files/default-copyright
b/meta-isar/recipes-app/example-raw/files/default-copyright
new file mode 100644
index 00000000..9c04255a
--- /dev/null
+++ b/meta-isar/recipes-app/example-raw/files/default-copyright
@@ -0,0 +1,15 @@
+Format: https://www.de
<https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/>
bian.org/doc/packaging-manuals/copyright-format/1.0/
<https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/>
+Upstream-Name: ${PN}
${BPN}
+Upstream-Contact: Mentor Embedded <embedded...@mentor.com>
${MAINTAINER}
+Source: https://github.com/MentorEmbedded/industrial-core
${HOMEPAGE}
+
+Files: *
+Copyright: 2022, Siemens
Copyright: ${MAINTAINER}
+License: Siemens
Need one template per OSS license, we keep this license in-house
+ .
+ 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
diff --git a/meta/classes/debianize.bbclass
b/meta/classes/debianize.bbclass
index 16f3638d..6039e869 100644
--- a/meta/classes/debianize.bbclass
+++ b/meta/classes/debianize.bbclass
@@ -121,6 +121,10 @@ deb_debianize() {
else
deb_create_rules
fi
+ # Add the copyright if unpacked sources does not contain copyright file
+ if [ ! -f ${S}/debian/copyright ] && [ -f ${WORKDIR}/default-copyright ];
then
+ install -v -m 644 ${WORKDIR}/default-copyright ${S}/debian/copyright
+ fi
# prepend a changelog-entry unless an existing changelog file already
# contains an entry with CHANGELOG_V
deb_add_changelog
--
2.34.1
[-- Attachment #1.2: Type: text/html, Size: 7489 bytes --]
next prev parent reply other threads:[~2024-03-14 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 5:44 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 [this message]
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-02-29 19:14 ` Florian Bezdeka
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=13f40102-3123-4d54-a5cc-f94e308b0c26n@googlegroups.com \
--to=srinuvasan.a@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