Re: Question about Pakfire Update process

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]

Hi Timmothy,

On Sun, 2015-03-22 at 10:43 +0100, IT Superhack wrote:
> Hi everybody,
> 
> I am currently working on bug #10767.

thanks for looking into this.

> During the last week, I wrote a shell script which compares the
> running kernel to the installed kernel files (/boot/...). If they are
> different, it recreates the files "boot.script" and "boot.scr".
> Because of that, the user doesn't have to do this after every kernel
> update.

I do not really get what this script is supposed to do. In case of an
update, the boot.script file will be overwritten any way. The version
with the binary header can then be created at build time.

What are you exactly trying to solve here?

> However, the script needs to be triggered after a kernel update took
> place. (Of course, I could copy it into /etc/cron.hourly/, but in my
> opinion, this is not a good solution.) I guess it needs to be
> triggered by Pakfire after the update process is done.

Cron is never the solution.

> Now comes my question: How do I do this? How can I tell Pakfire to run
> a custom shell script after an update?
> 
> I would be very greatful if you could mail me some hints.
> 
> Best regards,
> Timmothy Wilson
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]