Currently all targets of rumpbake are hardcoded. That means I can't
control what rump components are linked in to the final binary. That's
not very desirable for power users. Being the first one to have such
needs I can certainly foresee other users in the future want to do the
I would like to make rumpbake more flexible. That could be done by
either getting rid of the positional arguments or making it accept user
provided config file.
The syntax of rumpbake being experimental means we can get away with any
breakage at this stage.