| 1 |
On Sun, Nov 13, 2011 at 8:59 AM, Thomas Sachau <tommy@g.o> wrote: |
| 2 |
> You expect people to manually check the build.log just to see, where it hangs? I prefer checking the |
| 3 |
> console, there i can see it directly and dont have to check for the path of the current build.log |
| 4 |
> and then have to additionally open it manually. |
| 5 |
|
| 6 |
I do think this is a fair point. It is pretty common practice in |
| 7 |
tasks that are expected to take a long time to have some kind of |
| 8 |
progress indicator. Even if it just means echoing a period every 10 |
| 9 |
seconds, or every 10 files, or whatever, it would be a nice way to |
| 10 |
tell that something is happening. I think we used to have a spinner, |
| 11 |
which would also work, especially if it is somehow tied to forward |
| 12 |
progress on the build.. |
| 13 |
|
| 14 |
Most binary distros don't do this, but it doesn't ever take them 15 |
| 15 |
minutes to install one package. |
| 16 |
|
| 17 |
Another useful thing might be to print out the path of the build logs |
| 18 |
each time a package starts building. That would make tailing a log of |
| 19 |
interest easier than hunting through them all. |
| 20 |
|
| 21 |
Rich |
Archives