You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.install scripts are discouraged whenever possible and treated somewhat of a last resort. In this case, it is possible to use a pacman hook (e.g.: in /usr/share/libalpm/hooks) that runs holo apply when a new files are placed into /usr/share/holo/files/ (or updated, or removed). The hook can be provided by the holo package itself, and also allows non-holo packages to just slip in holoscripts and alike.
This would also ensure that holo apply one gets run once per transaction after packages are installed, rather than once per package.
The hook would be quite trivial, and is a bit more of a declarative (rather than imperative) approach. A vague (poorly tested) sample is something like:
Currently,
holoscripts
get run by basically including this.install
script in each package:.install
scripts are discouraged whenever possible and treated somewhat of a last resort. In this case, it is possible to use a pacman hook (e.g.: in/usr/share/libalpm/hooks
) that runsholo apply
when a new files are placed into/usr/share/holo/files/
(or updated, or removed). The hook can be provided by theholo
package itself, and also allows non-holo packages to just slip inholoscripts
and alike.This would also ensure that
holo apply
one gets run once per transaction after packages are installed, rather than once per package.The hook would be quite trivial, and is a bit more of a declarative (rather than imperative) approach. A vague (poorly tested) sample is something like:
I will try and make a PR with this, but would like to hear any thoughts or feedback you may have before further digging into this.
The text was updated successfully, but these errors were encountered: