| 1 |
Justin R Findlay wrote: |
| 2 |
> <ctrl>-s, <ctrl>-q seems to work for me. |
| 3 |
|
| 4 |
This means one still has to monitor the output. |
| 5 |
|
| 6 |
> In my /etc/make.conf I have: |
| 7 |
> |
| 8 |
> PORTAGE_ELOG_CLASSES="info warn error log" |
| 9 |
> PORTAGE_ELOG_SYSTEM="mail syslog" |
| 10 |
> PORTAGE_ELOG_MAILURI="root@××××××××.us" |
| 11 |
|
| 12 |
Thank you for pointing this out. It is a new stuff for me. I'll |
| 13 |
investigate the documentation and give it a try. |
| 14 |
|
| 15 |
--snip |
| 16 |
|
| 17 |
> If you tell it to, portage will log every last |
| 18 |
> configure and gcc statement spewed forth on the command line into |
| 19 |
> /var/log/portage/. |
| 20 |
|
| 21 |
Yes, I already have about 400MB of logs there. I still wonder when will |
| 22 |
come the day I'll wipe them out. :) |
| 23 |
|
| 24 |
> Gentoo generally overwrites C(XX)FLAGS only when they are problematic |
| 25 |
> (unpredictable or cause breakage) for certain platforms/packages. If |
| 26 |
> you have a customized ebuild you can always drop it into your own |
| 27 |
> overlay. Mine is in /usr/local/portage. If you have multiple overlays |
| 28 |
> you can use gensync from the gentoolkit-dev package to sync with them. |
| 29 |
> |
| 30 |
|
| 31 |
|
| 32 |
The truth is there are only a few ebuilds I want to change something in. |
| 33 |
Up to now in case I want to change something or the packages doesn't |
| 34 |
compile the normal way, my practice is to use "ebuild `equery w |
| 35 |
package-name` unpack", do my things in the temp dir, compile manually, |
| 36 |
put a file ".compiled" and resume the installation. |
| 37 |
May be I'll start using my own overlay after I collect "enough" packages. |
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
Best regards, |
| 42 |
Daniel |
| 43 |
|
| 44 |
-- |
| 45 |
gentoo-user@g.o mailing list |
Archives