On Saturday 14 February 2009 07:51:39 Ciaran McCreesh wrote: > Which of these options sounds most useful as a default behaviour for > foreground and exclusive builds? > > 3) Output to stdout / stderr, also keep build logs in a file, and keep > any e* messages in a different file. ------ Option 3 here is what I would like to see. As stated in previous responses having the build log will aid greatly in debugging any problems. But more importantly the e* messages. I really do want to see those kept in a separate file. On some builds I will sit and watch to look for messages, but on the longer builds, like KDE, OpenOffice I will often start the build before I go to bed and check on the results the next day. ------ > Which of these options sounds most useful as a default behaviour for > background and parallel actions? >
> iv) Output to build logs only. Show when we start or complete a task > to stdout. If a task has been running for $to_be_determined seconds, > show a status message saying it's still going. > ------ to iv I would add show the tail of the failed log on error and have your status message periodically show how long the build has been running. ------ > > This is not a vote. Reasoned opinions count. _______________________________________________ paludis-user mailing list [email protected] http://lists.pioto.org/mailman/listinfo/paludis-user
