From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [patch 1/1] linux module postinst generalisation
Date: Mon, 19 Sep 2022 11:08:36 +0200 [thread overview]
Message-ID: <CAJGKYO7kXBk1dh7siZkWfAGadarFDtqmRJy_D18yhCQw_ZuPjw@mail.gmail.com> (raw)
In-Reply-To: <20220919093104.41eb5568@md1za8fc.ad001.siemens.net>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
Il Lun 19 Set 2022, 09:31 Henning Schild <henning.schild@siemens.com> ha
scritto:
> Hey Roberto,
>
> [...]
>
And an interator over multiple directories would maybe also fail once
> it finds the one "broken" directory.
>
One iteration might fail but nicely because others succeed. Yes, in theory
should not be found any invalid entry in that folder but integraring 3rd
party proprietary packages, it could happen and it is much easier to
generalise the approach rather than fix that packages.
Moreover, why not something like
depmod -a ${KERNEL_VERSION}
After all, the opposite of a generalisation is a specific call that cannot
fails.
I hope this helps, R-
[-- Attachment #2: Type: text/html, Size: 1604 bytes --]
prev parent reply other threads:[~2022-09-19 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM0PR10MB2020627F69E1644392B6677CAA489@AM0PR10MB2020.EURPRD10.PROD.OUTLOOK.COM>
2022-09-16 12:42 ` [patch 1/1] image tools extention not install suggested deb Roberto A. Foglietta
2022-09-16 12:44 ` [patch 1/1] linux module postinst generalisation Roberto A. Foglietta
2022-09-19 7:31 ` Henning Schild
2022-09-19 9:08 ` Roberto A. Foglietta [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=CAJGKYO7kXBk1dh7siZkWfAGadarFDtqmRJy_D18yhCQw_ZuPjw@mail.gmail.com \
--to=roberto.foglietta@gmail.com \
--cc=henning.schild@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