|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I had to think long and hard about where to put this :/
Putting it where it should be logically:
* pkg_setup:
Downsides: new phase function people won't expect to be there
Downsides: makes extra work for the common definition of pkg_setup
* src_unpack:
Downsides: Same as pkg_setup
* src_pretend:
Downsides: Too early
Downsides: makes all perl modules slow to install
* global
Downsides: makes metadata collection very slow
Downsides: risks running too much code in global scope
* src_configre:
Downsides: risks only discovering the bug after shipping
However, the case of the last one dictates that the maintainer did
significant changes, and then never even compile tested it.
Maintainer rightly gets a rap over the knuckles and such things should
never be stable
|