Hooks can accept a command-chain:
- if the hook was "installed" through a part we probably want to add the snapcraft-runner script into command-chain as we do for apps (I believe we do this already in the form of a wrapper and we need to upgrade to command chain)
- if the hook was in the project root ($PROJECT_ROOT/snap/hooks/remove) then it is assumed you setup everything correctly and we just copy it over.
This behavior has not changed for hooks.
We don't add environment as it is not a list and there would be no easy way to override for a developers point of view.
Hooks can accept a command-chain: ROOT/snap/ hooks/remove) then it is assumed you setup everything correctly and we just copy it over.
- if the hook was "installed" through a part we probably want to add the snapcraft-runner script into command-chain as we do for apps (I believe we do this already in the form of a wrapper and we need to upgrade to command chain)
- if the hook was in the project root ($PROJECT_
This behavior has not changed for hooks.
We don't add environment as it is not a list and there would be no easy way to override for a developers point of view.
Silently failing hooks is a snapd issue.