From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
To: "Moessbauer, Felix (T CED OES-DE)" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [RFC PATCH 0/2] debianize: Use dh_installsystemd
Date: Thu, 1 Feb 2024 16:48:47 +0100 [thread overview]
Message-ID: <0a255521-8382-4e2f-a94a-eae8d897e6e3@siemens.com> (raw)
In-Reply-To: <aba88aa6800dba625edea1a80db0023bca8a8af4.camel@siemens.com>
On 2/1/24 16:16, Moessbauer, Felix (T CED OES-DE) wrote:
> On Thu, 2024-02-01 at 14:07 +0100, 'Quirin Gylstorff' via isar-users
> wrote:
>> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>>
>> This series adds the variable DEBIAN_SYSTEMD_SERVICE which defines
>> a systemd file to automatically be added to the debian folder and
>> automatically installed by using `dh_installsystemd`.
>
> Hi, do we really need that interface?
>
> Usually you just copy these files into the debian folder in
> do_prepare_build. That's it.
>
> There are also more files which get picked up by the debhelpers.
We have multiple location and files where the do_install pattern is
used:
```
file://postinst"
"
do_install() {
install -d -m 755 ${D}/lib/systemd/system
install -m 644 ${WORKDIR}/enable-fsck.service ${D}/lib/systemd/system/
```
If the the do_prepare_build pattern is sufficient we can also change all
service:
```
do_prepare_build:append() {
install -m 644 ${WORKDIR}/enable-fsck.service ${S}/debian
}
```
Quirin
>
> Best regards,
> Felix
>
>>
>> Quirin Gylstorff (2):
>> debianize: use dh_installsystemd to automatically add systemd
>> service
>> meta/recipe-support: Use DEBIAN_SYSTEMD_SERVICE variable
>>
>> meta/classes/debianize.bbclass | 15
>> +++++++++++++++
>> meta/recipes-support/enable-fsck/enable-fsck.bb | 6 ++----
>> meta/recipes-support/enable-fsck/files/postinst | 3 ---
>> .../expand-on-first-boot_1.4.bb | 7 ++-----
>> .../expand-on-first-boot/files/postinst | 3 ---
>> .../sshd-regen-keys/sshd-regen-keys_0.4.bb | 1 +
>> 6 files changed, 20 insertions(+), 15 deletions(-)
>> delete mode 100644 meta/recipes-support/enable-fsck/files/postinst
>> delete mode 100644 meta/recipes-support/expand-on-first-
>> boot/files/postinst
>>
>> --
>> 2.43.0
>>
>
next prev parent reply other threads:[~2024-02-01 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 13:07 Quirin Gylstorff
2024-02-01 13:07 ` [RFC PATCH 1/2] debianize: use dh_installsystemd to automatically add systemd service Quirin Gylstorff
2024-02-01 13:07 ` [RFC PATCH 2/2] meta/recipe-support: Use DEBIAN_SYSTEMD_SERVICE variable Quirin Gylstorff
2024-02-01 15:16 ` [RFC PATCH 0/2] debianize: Use dh_installsystemd MOESSBAUER, Felix
2024-02-01 15:48 ` Gylstorff Quirin [this message]
2024-02-01 15:52 ` Anton Mikanovich
2024-02-15 8:42 ` MOESSBAUER, Felix
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=0a255521-8382-4e2f-a94a-eae8d897e6e3@siemens.com \
--to=quirin.gylstorff@siemens.com \
--cc=felix.moessbauer@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