Bundle does not run postinstallcmds per component

[sam-maloney]

As far as I can tell, the bundle EasyBlock does not run any postinstallcmds, but just silently ignores them. The only way I can currently see to run such commands "post install" is to abuse the sanity_check_commands...

Is there a better way to work around this, or could Bundle be modified to actually honour postinstallcmds?

[boegel]

@sam-maloney Which EasyBuild version are you using here? Also, with which easyconfig file are you seeing this?

I'm pretty sure that postinstallcmds is being run, because we rely on it for example the existing Xvfb-21.1.18-GCCcore-14.2.0.eb easyconfig, for which the trace output shows:

== postprocessing...
  >> running shell command:
        chmod u+w xvfb-run && cp -a xvfb-run /software/Xvfb/21.1.18-GCCcore-14.2.0/bin/ && chmod a+x
/software/Xvfb/21.1.18-GCCcore-14.2.0/bin/xvfb-run
        [started at: 2026-08-07 10:38:49]
        [working dir: /tmp/easybuild_build/Xvfb/21.1.18/GCCcore-14.2.0/xorg-server-21.1.18]
        [output and state saved to /tmp/eb-6vix2prp/run-shell-cmd-output/chmod-ao2lgq91]
  >> command completed: exit 0, ran in < 1s
== ... (took < 1 sec)

[sam-maloney]

Ah, thank you for providing the example usage; I was specifying the postinstallcmds alongside the other build parameters for the individual component rather the at the level of the outer bundle, and they are not run per component.

In my use case either placement is fine, but I would note that this is niether intuitive nor well-documented, it is just silently ignored, which was very frustrating to debug 🙃. And the current behaviour would preclude use cases where one actually needed to run some command between the install of one component and the build of another.

My specific problem is solved, but I'll leave it up to you whether to close this issue or if you think running the postinstallcmds per component would be a worthwhile feature to have.