Mojolicious-branch integration tracker
I want to use this issue to track anything I need to fix before I can merge the Mojolicious branch.
AFAICS:
-
Make it as easy to use as the current master
branch (implemented by pre-installing Mojolicious) -
Testing to make sure it works at least as well -
U/I at least as good (see screenshot for what it's like now) -
Understandable by devs not named @mpyne -
Build context phases applied based on options rather than cmdline-only (right now you can't do things like manual-update at global level and have the right effect). -
Understandable error messages with missing module names -
Understandable error messages with invalid cmdline flags. -
Test what --debug
does -
Colorize entire module result lines in output. -
Use PASS/FAIL as readable results w/out need for color. -
--stop-on-failure
doesn't say non-built modules "built OK" -
Introspection commands like --query. -
Proper errors instead of croak_*
. UI frontends won't like the backend just suiciding and we don't want them to turn into complicated process supervisors. -
Look at weird error message you get from rc-file breakage (e.g. remove the '#' character from a comment -
Fix crash when using --install
(I think I assume a 'build' promise will exist which is apparently not the case here). -
Fix persistent option handling in subprocess (as I fixed it in commit 76a8ee1b) -
Re-fix persistent options? (compiling palapeli shows 4073 warnings but only saves 0)
-
-
Issue #66 (closed), closing browser tab on event viewer crashes the server -
The event_viewer
log file does not appear to get saved in--backend
mode. -
Ensure the interactive prompt for an existing lockfile is handled properly in --backend
mode. (Need to look in general for all input prompts, I think :( ) -
kdesrc-build --no-src
crashes.--src-only
works. -
What else?
Once we can merge Mojolicious I think we can then spec out and implement a useful API for other client programs to use to replace the kdesrc-build CLI/text interface.
Edited by Michael Pyne