1 |
In order to facilitate better ease of use with phase hooks, I propose a |
2 |
paludis-style default phase hook. Basically ebuild.sh provides a default |
3 |
hook that looks in PORTAGE_HOOKS_DIR/{pre,post}_${EBUILD_PHASE}/ for shell |
4 |
scripts and sources them. |
5 |
|
6 |
The patch to ebuild.sh only generates hooks 1 phase at a time. People |
7 |
with existing hooks in bashrc will not be affected (the bashrc hooks will |
8 |
over-ride these default hooks). |
9 |
|
10 |
The motivation here is to have users create functionality in these hooks |
11 |
and enable them to easily share hooks. 'hey drop this hook in location X' |
12 |
is a lot easier than 'add this hook to bashrc...oh and make sure you don't |
13 |
already have a post_pkg_prerm hook in there...oh and make sure if you do |
14 |
have an existing hook you make it so that both run...' and so forth. |
15 |
|
16 |
For people with no hooks the speed penalty is nil; for those with many |
17 |
hooks, there is probably some small overhead per phase as the script |
18 |
enumerates and sources the hooks. |
19 |
|
20 |
Comments and Questions are welcome. |
21 |
|
22 |
-Alec Warner |