| 1 |
Apparently, though unproven, at 16:10 on Saturday 21 August 2010, Carl Pettit |
| 2 |
did opine thusly: |
| 3 |
|
| 4 |
> A lot of ebuilds list a fixup script at the end that the user must manually |
| 5 |
> execute. If the build is pulled in as part of another build, these scripts |
| 6 |
> can be missed. This fact has cost me 2 days and a borked system. Is there a |
| 7 |
> way of running these automatically on completion as part of the install? |
| 8 |
|
| 9 |
|
| 10 |
No, there is no such thing and will likely never be. |
| 11 |
|
| 12 |
The default operation of gentoo is to put stuff there and wait for you (root) |
| 13 |
to take action on it. |
| 14 |
|
| 15 |
ebuilds do configure dick with your configs (OK, except webmin, but that is a |
| 16 |
piece of shit and to be expected), start daemons or cause them to be added to |
| 17 |
rc-update. That is for YOU - as root - to decide and act on. User wanting a |
| 18 |
distro that does everything for them need use Red Hat, Ubuntu, etc. |
| 19 |
|
| 20 |
What you must do is configure your elogging in make.conf (it's all in man 5 |
| 21 |
make.conf) and read the elogs in /var/log/portage/elog/ when an emerge is |
| 22 |
complete. Or have them mailed to you. |
| 23 |
|
| 24 |
-- |
| 25 |
alan dot mckinnon at gmail dot com |
Archives