Hi, today I started the elog process for my portage and found this little error in the docs. Portage will NOT store the logfile in PORT_LOGDIR/elog it will store it in PORT_LOGDIR. I'm using portage2.2-rc16 and I don't know does the older version of portage do it. reagards j0inty Reproducible: Always
We document stable Portage behavior, not ~arch. If this is still the case when Portage-2.2 goes stable, we'll take another look at the handbook.
Except that 2.1.6 is to get stable "soon"... Portage guys, could you please verify the original report?
(In reply to comment #0) > Portage will NOT store the logfile in PORT_LOGDIR/elog it will store it in > PORT_LOGDIR. Well, there are are to kinds of logs. The complete build logs are saved directly in $PORT_LOGDIR. The logs that contain elog messages alone are saved in $PORT_LOGDIR/elog. I think that you just haven't the difference between the two types of logs. Can you confirm?
(In reply to comment #3) > (In reply to comment #0) > > Portage will NOT store the logfile in PORT_LOGDIR/elog it will store it in > > PORT_LOGDIR. > > Well, there are are to kinds of logs. The complete build logs are saved > directly in $PORT_LOGDIR. The logs that contain elog messages alone are saved > in $PORT_LOGDIR/elog. I think that you just haven't the difference between the > two types of logs. Can you confirm? > Yes you are right. I had a look on it and saw that the logs will store directly to PORT_LOGDIR and the elog message under PORT_LOGDIR.
Not a bug, then. The make.conf.example that ships with Portage-2.1.6 confirms that the handbook is still correct, namely: If you have specified PORT_LOGDIR in make.conf, then elog saves messages to $PORT_LOGDIR/elog. If you have not set PORT_LOGDIR, then elog will save messages to /var/log/portage/elog. If you set PORT_LOGDIR to /random/logation, then elog will save to /random/location/elog. Either way, there will still be a separate elog directory that messages are saved to.