| Summary: | no documentation on the elog functions | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | John <Darkintent> |
| Component: | Documentation | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | antarus, aross, gentoo, mjevans1983, zlin |
| Priority: | High | Keywords: | InVCS |
| Version: | 2.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 216231 | ||
|
Description
John
2005-12-19 02:37:18 UTC
the version information is irrelevant what exactly needs to be documented here ? i see: make.conf(5): PORTAGE_ELOG_CLASSES PORTAGE_ELOG_SYSTEM PORTAGE_ELOG_COMMAND PORTAGE_ELOG_MAILURI anything else ? Those entries are not listed when I do man make.conf and I just updated this morning. What you listed does appear in the sample make.conf file however it still is not entirely clear how to use each feature. I suggested on the mailing list that there should be a howto created for these specific features. antarus/spanky, game for this? not a regression. I've tried all these, NOTHING seems to create a file at all. Would another emerge running at the same time prevent this change from taking effect in say emerge gotmail ? (or do I need to test these against some other package?)
The documentation isn't really helpfull either in that it doesn't give me a WORKING example.
It Seems like it's calling a log Processor after the entire ${LOGFILE} is created... so the second to last option or PORTAGE_ELOG_COMMAND="cp ${LOGFILE} /root/elogs/$(date '+%Y%M%d')-${PACKAGE}" would be closer to what I desire...
Portage 2.1_pre7-r5 (default-linux/x86/2005.0, gcc-3.4.6, glibc-2.4-r1, 2.6.16-rc6-mm2 i686)
PORTAGE_ELOG_CLASSES="warn error log"
PORTAGE_ELOG_SYSTEM="save custom"
#PORTAGE_ELOG_COMMAND="/bin/sed -e 's/^/${PACKAGE}: /' '${LOGFILE}' >> /root/elogs/$(date '+%Y%M%d')"
#PORTAGE_ELOG_COMMAND="echo > ${LOGFILE}-$(date '+%Y%M%d')"
#PORTAGE_ELOG_COMMAND="cp ${LOGFILE} /root/elogs/$(date '+%Y%M%d')"
PORTAGE_ELOG_COMMAND="touch /root/if-this-file-is-here-then-it-got-executed"
Ehm, are you saying that no logfile is created for you on `emerge gotmail`? That's because gotmail doesn't have any messages that could be logged. If you want a full buildlog use PORT_LOGDIR instead. > What you listed does appear in the sample make.conf file however it still is
> not entirely clear how to use each feature. I suggested on the mailing list
> that there should be a howto created for these specific features.
>
not a howto but elog should be in some man page or have it's own. because i went through all portage documentation in the man pages and there is no elog documentation.
(In reply to comment #2) > what exactly needs to be documented here ? i see: > > make.conf(5): > PORTAGE_ELOG_CLASSES > PORTAGE_ELOG_SYSTEM > PORTAGE_ELOG_COMMAND > PORTAGE_ELOG_MAILURI > > anything else ? PORTAGE_ELOG_MAILFROM PORTAGE_ELOG_MAILSUBJECT *** Bug 153503 has been marked as a duplicate of this bug. *** Added a dummy section to make.conf(5) that points to make.conf.example as temporary solution (final solution would be to generate both files from the same source). If anyone wants to write a real patch for make.conf.5 attach it here. This is supposed to be fixed in portage-2.2_pre5 or earlier. This is supposed to be fixed in portage-2.2_pre5 or earlier. |
