From: srinuvasan.a@siemens.com
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, ubely@ilbers.de,
Srinuvasan A <srinuvasan.a@siemens.com>
Subject: [PATCH v5 2/2] doc/user_manual: add a section for debianize class
Date: Wed, 13 Mar 2024 11:27:12 +0530 [thread overview]
Message-ID: <20240313055712.3883100-1-srinuvasan.a@siemens.com> (raw)
In-Reply-To: <f7cd0b58-eca0-44f3-b459-71c6f86256c5@siemens.com>
From: Srinuvasan A <srinuvasan.a@siemens.com>
Add additional information about debianize class for generating the
required files under debian directory.
Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
---
doc/user_manual.md | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/doc/user_manual.md b/doc/user_manual.md
index bc730243..3e356df0 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -907,6 +907,14 @@ The shell function `deb_debianize` creates a `debian` folder. But it will not ov
Have a look at meta-isar/recipes-app/samefile/samefile_2.14.bb and meta/classes/debianize.bbclass for an example and the implementation.
+Here ISAR's debianize class generates the following files:
+
+ - Create control file if sources does not contain a control file
+ - Create rules file if sources does not contain a rules file
+ - Add the copyright if unpacked sources does not contain copyright file, please check the example-raw recipe
+ - Add the changelog and hooks( pre/post/inst/rm ) into the debian directories if WORKDIR contains the files
+
+
### Packages without source
If your customization is not about compiling from source there is a second way of creating `deb` packages. That way can be used for cases like:
--
2.34.1
next prev parent reply other threads:[~2024-03-13 5:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 7:22 [PATCH] meta/classes/debianize: Add copyright file to debian folder 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 ` srinuvasan.a [this message]
2024-03-13 8:38 ` [PATCH v5 " 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 ` [PATCH] " 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=20240313055712.3883100-1-srinuvasan.a@siemens.com \
--to=srinuvasan.a@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=ubely@ilbers.de \
/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