Run the expected hooks on build and install and let users extend buildInputs (when switching to nativeBuildInputs). Shadowed the run shellCommand with a shell function, this is so a trap can be defined in the shell to shut down mdbook when exiting the shell.
~If someone has a smart idea of how to use the shell command I'm all ears. Problem with just putting it there is that mdbook is started in the background from the shell command program, so the trap would either run to early (when run finishes) or not at all. Kept the shellCommand to get the printed description.~
Run the expected hooks on build and install and let users extend buildInputs (when switching to nativeBuildInputs). Shadowed the run shellCommand with a shell function, this is so a trap can be defined in the shell to shut down mdbook when exiting the shell.
~If someone has a smart idea of how to use the shell command I'm all ears. Problem with just putting it there is that mdbook is started in the background from the shell command program, so the trap would either run to early (when
runfinishes) or not at all. Kept the shellCommand to get the printed description.~