On Sun, Nov 13, 2011 at 8:59 AM, Thomas Sachau <tommy@g.o> wrote:
> You expect people to manually check the build.log just to see, where it hangs? I prefer checking the
> console, there i can see it directly and dont have to check for the path of the current build.log
> and then have to additionally open it manually.

I do think this is a fair point.  It is pretty common practice in
tasks that are expected to take a long time to have some kind of
progress indicator.  Even if it just means echoing a period every 10
seconds, or every 10 files, or whatever, it would be a nice way to
tell that something is happening.  I think we used to have a spinner,
which would also work, especially if it is somehow tied to forward
progress on the build..

Most binary distros don't do this, but it doesn't ever take them 15
minutes to install one package.

Another useful thing might be to print out the path of the build logs
each time a package starts building.  That would make tailing a log of
interest easier than hunting through them all.

Rich