| 1 |
I've been working on creating an ebuild this week and after working with it I |
| 2 |
have some questions about how ebuilds work. |
| 3 |
|
| 4 |
1. I assume that if I add no functions to an ebuild the process is A) |
| 5 |
src_unpack, B) src_compile, C) src_install. In other words there are three |
| 6 |
steps or functions that will be executed. If I desire I can make my own |
| 7 |
functions for these but if I don't I get these three steps executed by emerge. |
| 8 |
|
| 9 |
2. What is the best way to let the user know what's happening - for example, |
| 10 |
"compiling xyz module now". I notice some builds use einfo to put out |
| 11 |
messages about what you have to do after install (add user to groups, etc). |
| 12 |
Are there specific ebuild functions I should use or are plain old echo |
| 13 |
statements okay? |
| 14 |
|
| 15 |
|
| 16 |
Thanks. |
| 17 |
|
| 18 |
-- |
| 19 |
|
| 20 |
Brett I. Holcomb |
| 21 |
AKA Grunt <>< |
| 22 |
|
| 23 |
-- |
| 24 |
gentoo-dev@g.o mailing list |
Archives