| 1 |
On Thursday 14 July 2005 20:58, Ned Ludd wrote: |
| 2 |
> echo "being that no portage dev in his/her right mind would ever" |
| 3 |
> echo "allow interactive code in an ebuild we use bashrc tricks" |
| 4 |
|
| 5 |
Actually, I promote interactive code in pkg_config(). There's no standard as |
| 6 |
to what it will do, so there's no real solution other than telling the user |
| 7 |
and then waiting for confirmation. |
| 8 |
|
| 9 |
As for the other phases, they should of course be 100% non-interactive. |
| 10 |
However, a pkg_presetup() or some such couldn't go astray - as long as it was |
| 11 |
purely optional. It would be much better to wait until portage supports |
| 12 |
arbitrary per-package env for it to be of any real use though. |
| 13 |
|
| 14 |
Regards, |
| 15 |
Jason Stubbs |
Archives