| 1 |
Geert Bevin wrote: [Mon Nov 19 2001, 5:42:34AM EST] |
| 2 |
> Typically a package has a configuration phase which occurs after merging |
| 3 |
> it into the system. This configuration is optional, but could be done |
| 4 |
> both for binary as source packages. |
| 5 |
|
| 6 |
Usually, portage addresses this by providing good defaults and then |
| 7 |
documentation for less standard configuration. If you need something to |
| 8 |
be executed (non-optionally) after merge, you can define a |
| 9 |
pkg_postinst() function in your ebuild. I think this addresses a large |
| 10 |
percentage of the cases without adding a more complex mechanism. |
| 11 |
|
| 12 |
Some sort of post-install user interaction has been discussed, with |
| 13 |
everything from an interactive config GUI to listing recommended |
| 14 |
documentation. This may be written eventually, but the set of possible |
| 15 |
solutions is large, diverse, and heavily dependant on personal taste, |
| 16 |
all of which tend to slow down the actual writing of code. |
| 17 |
|
| 18 |
--Chouser |
Archives