[Yum-devel] log installroot in file log

seth vidal skvidal at fedoraproject.org
Thu Oct 18 13:05:56 UTC 2007


On Thu, 2007-10-18 at 14:56 +0200, Florian Festi wrote:
> seth vidal wrote:
> > On Thu, 2007-10-18 at 10:18 +0200, Florian Festi wrote:
> >> seth vidal wrote:
> >>> On Wed, 2007-10-17 at 14:50 -0400, James Antill wrote:
> >>>
> >>>>  Who asked for this, and did they give a problem they are trying to
> >>>> solve by it?
> >>> chroot handling from outside.
> >>>
> >>>>  I think a better solution is to use a different log file when using a
> >>>> custom installroot, so maybe they'd be happy with a --logfile cmd line
> >>>> option?
> >>> well, when we're operating on a chroot that's already existent we write
> >>> to $chroot/var/log/yum.log
> >>>
> >>> if the chroot isn't there, yet, we write to /var/log/yum.log so that it
> >>> gets recorded somewhere. 
> >> This might be the real problem. What about either just create 
> >> $chroot/var/log/yum.log when needed (might turn out to be fishy) or complain 
> >> if it isn't accessible and exit.
> >>
> >> This "yeah, we logged it... somewhere" thing is asking for trouble.
> > 
> > the complaint I've heard is:
> >  "we make chroots and immediately destroy them but we still want a log
> > of what went on"
> 
> cp?

umm what does 'cp' mean here? Are you saying that they should run mock
then 'cp' the yum.log file out before they nuke the chroot?

-sv





More information about the Yum-devel mailing list