Quick question for mock users

[Clark Williams]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

While working on a cross compilation project that uses mock to manage a
long-term chroot, I got quite annoyed that when mock throws an error due
to a failed command, I would have to go dig into the log files to find
what went wrong. It occurred to me that since there's error output going
out from an exception, there *shouldn't* be a problem with printing the
output of the failing command on stderr.

So the question to users of mock (especially the plague folks):

Will adding the error output of a failed command to the stderr stream
from mock cause problems to programs calling mock?

Thanks,
Clark
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFFyO4YHyuj/+TTEp0RAoS/AJ9qCwisXA43dMU4DGGAUdHocnOeKgCfejM4
> 2bCFKihmCi+LDYj8dmevVWg=
> =KZw0
> -----END PGP SIGNATURE-----

[Mike McLean]

Clark Williams wrote:
> Will adding the error output of a failed command to the stderr stream
> from mock cause problems to programs calling mock?

I don't believe it will matter to Koji.

[Clark Williams]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike McLean wrote:
> Clark Williams wrote:
> > Will adding the error output of a failed command to the stderr stream
> > from mock cause problems to programs calling mock?
>
> I don't believe it will matter to Koji.

Works for me. Next version (0.6.11) will have this in it.

Clark
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFFygIjHyuj/+TTEp0RAlHaAJ4/Js8YPB8AWjIxq0LpSq3KPjujWQCgp1T8
> m7myFJu2zXbcBdB6rLlHGko=
> =o+Me
> -----END PGP SIGNATURE-----