solus-project / package-management

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[Question] Post Install Actions/Scripts

QORTEC opened this issue · comments

I would like to add/modify post eopkg install actions to more suite my needs/wants.
Could you point me towards documentation or code responsible for this process?

 [✓] Syncing filesystems                                                success
 [✓] Updating dynamic library cache                                     success
 [✗] Updating clr-boot-manager                                           failed

A copy of the command output follows:

[ERROR] cbm (../src/lib/system_stub.c:L31): Invalid block device: 0:29
Out of memory
[FATAL] cbm (../src/bootman/bootman.c:L477): Cannot determine boot device


 [✗] Updating clr-boot-manager                                           failed

A copy of the command output follows:

[ERROR] cbm (../src/lib/system_stub.c:L31): Invalid block device: 0:29
Out of memory
[FATAL] cbm (../src/bootman/bootman.c:L477): Cannot determine boot device


 [✓] Updating icon theme cache: hicolor                                 success
 [✓] Updating desktop database                                          success
 [✓] Updating manpages database                                         success

I'm a Solus user running on a unsupported file system:

  1. I would like to change the kernel update code to launch a script that supports my file system
  2. I would like to take snapshots after every update to enable rollback (unless its possible to do it Pre Install)

I haven't been able to figure out whats the mechanism responsible for running these tasks.

Post Install on Solus seems to be done via usysconf. To add/edit additional functionality will require direct modification of usysconf binary which is written in C.

Therefore I can conclude that:

  1. eopkg does not have a Pre/Post Install function
  2. adding/editing triggers in usysconf is not easily done (due to the required C knowledge)
  3. this is probably not a planed feature, and therefor out of scope for eopkg