Bugzilla Bug 116018

The manual pages for portage-2.1_pre1 still refer to 2.0.51, hence they do not
contain information about things like elog and how to enable or otherwise use
the features added to this release specifically.

Emerge info:

Portage 2.1_pre1 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r3,
2.6.14-gentoo-r4 x86_64)
=================================================================
System uname: 2.6.14-gentoo-r4 x86_64 AMD Athlon(tm) 64 Processor 3200+
Gentoo Base System version 1.12.0_pre11
ccache version 2.4 [enabled]
dev-lang/python:     2.3.5, 2.4.2
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1-r1
sys-devel/libtool:   1.5.20-r1
virtual/os-headers:  2.6.11-r3
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env
/usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="PORT_LOGDIR autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X a52 aac alsa audiofile avi bash-completion berkdb bitmap-fonts
bzip2 cdr crypt cups curl dts dvd dvdr dvdread eds emboss encode esd exif expat
fam ffmpeg flac foomaticdb fortran freetype gdbm gif glut gmp gnome gpm
gstreamer gtk gtk2 hal howl idn imagemagick imlib ipv6 jpeg kde kdeenablefinal
lcms lzw lzw-tiff mad matroska mng mozilla mp3 mpeg ncurses nls nptl nptlonly
ogg opengl pam pcre pdflib perl png postgres python qt quicktime readline ruby
sdl spell ssl tcpd theora tiff truetype truetype-fonts type1-fonts udev usb
userlocales vorbis xine xml2 xpm xv xvid zlib elibc_glibc kernel_linux
userland_GNU"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

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.