1. run validator (issue574)
2. handle single-file PDDL input
3. handle compressed input (xz etc.)
4. handle pipelining between components (see also point 9. below)
5. refactor portfolio code, see issue414
6. when search is not run, options should go to first component being run by 
default
7. call translator as a module
8. rename --overall-{time,memory}-limit to --planner-{time,memory}-limit
9. let driver delete output.sas file (issue864)

Summary: make issue864 an item of its own (no. 9).

Summary: added reference to issue864 for the pipelining idea.

Explanation for Jendrik's last edit of the summary:

The motivation for the "overall" to "planner" limit name change is that we want
to introduce limits for the validator, too. What is currently called the
"overall" time limit is supposed to only apply to the planner itself, not the
validator, which makes "planner" a better word than "overall".

Not sure if this fits here since it would require more changes in the
translator, but you also mentioned that we might want to call the translator as
a module.

Refactoring the portfolio code is still 
current, though not pressing.

Here is an old list of ideas for our driver script that has never made it onto
the tracker:

1. optionally run validator
2. handle single-file PDDL input
3. handle compressed input (xz etc.)
4. handle pipelining between components
5. refactor portfolio code, see issue414 (is this still current?)
6. when search is not run, options should go to first component being run by default