Which of these options sounds most useful as a default behaviour for
foreground and exclusive builds?

1) Output to stdout / stderr only. (This is the current behaviour.)

2) Output to stdout / stderr only, and keep any e* messages in a file.

3) Output to stdout / stderr, also keep build logs in a file, and keep
any e* messages in a different file.

4) Output to stdout / stderr, also keep build logs in a file which is
removed if the build succeeds, and keep any e* messages in a different
file.

Which of these options sounds most useful as a default behaviour for
background and parallel actions?

i) Output everything all mixed up to stdout / stderr.

ii) Output to build logs only. Show when we start or complete a task to
stdout.

iii) Output to build logs only. Show when we start or complete a task to
stdout. On error, automatically show the tail of the failed log.

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.

v) 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 and automatically show
the tail of its build log (if there's anything new) as "this is what's
going on".

This is not a vote. Reasoned opinions count.

-- 
Ciaran McCreesh

Attachment: signature.asc
Description: PGP signature

_______________________________________________
paludis-user mailing list
[email protected]
http://lists.pioto.org/mailman/listinfo/paludis-user

Reply via email to