public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Cedric Hombourger <cedric.hombourger@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH] debianize: handle .triggers and .service files
Date: Tue, 26 Mar 2024 23:15:09 +0300	[thread overview]
Message-ID: <34d1355767bdea5f367ec7d061ec101b4fb02ddf.camel@ilbers.de> (raw)
In-Reply-To: <20231114195427.345320-1-cedric.hombourger@siemens.com>

On Tue, 2023-11-14 at 20:54 +0100, 'Cedric Hombourger' via isar-users
wrote:
> Some packages need to update/rebuild the initramfs and this is
> particularly
> slow on Debian systems (which are not using more modern technologies
> such
> as dracut or mkosi). Instead of having each package call update-
> initramfs,
> use a trigger instead to have dpkg defer that call to the very end of
> the
> transaction. Many packages also failed to rebuild the initramfs when
> the
> package gets removed. Demonstrate use with initramfs-fsck-hook-ext4.
> 
> Other packages ship systemd units and usually do this using
> do_install()
> and a postinst script. Such recipes also fail to handle the removal
> of
> such packages. By naming the unit ${PN}.service and putting it under
> debian/, debhelper will generate the necessary maintainer scripts
> (preinst, postinst, prerm, postrm).
> 
> Signed-off-by: Cedric Hombourger <cedric.hombourger@siemens.com>
> ---
>  meta/classes/debianize.bbclass                            | 8
> ++++++++
>  ...d-on-first-boot_1.4.bb => expand-on-first-boot_1.5.bb} | 6 +-----
>  meta/recipes-support/expand-on-first-boot/files/postinst  | 3 ---
>  .../files/{postinst => initramfs-fsck-hook-ext4.triggers} | 5 ++---
>  ...k-hook-ext4_0.1.bb => initramfs-fsck-hook-ext4_0.2.bb} | 2 +-
>  5 files changed, 12 insertions(+), 12 deletions(-)
>  rename meta/recipes-support/expand-on-first-boot/{expand-on-first-
> boot_1.4.bb => expand-on-first-boot_1.5.bb} (78%)
>  delete mode 100644 meta/recipes-support/expand-on-first-
> boot/files/postinst
>  rename meta/recipes-support/initramfs-fsck-hook/files/{postinst =>
> initramfs-fsck-hook-ext4.triggers} (51%)
>  rename meta/recipes-support/initramfs-fsck-hook/{initramfs-fsck-
> hook-ext4_0.1.bb => initramfs-fsck-hook-ext4_0.2.bb} (88%)
> 
Applied to next, thanks.

      parent reply	other threads:[~2024-03-26 20:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 19:54 Cedric Hombourger
2023-11-14 20:22 ` MOESSBAUER, Felix
2023-11-15  8:36   ` Jan Kiszka
2023-11-15  8:43     ` MOESSBAUER, Felix
2023-11-15  8:57       ` cedric.hombourger
2023-11-15  9:03         ` MOESSBAUER, Felix
2023-11-16 12:38       ` Jan Kiszka
2024-03-07  7:23 ` Uladzimir Bely
2024-03-26 20:15 ` Uladzimir Bely [this message]

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=34d1355767bdea5f367ec7d061ec101b4fb02ddf.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=cedric.hombourger@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