Using arara directives to automate lilypond-book and pdflatex

Question

This problem is similar to the one here and it is based on the referenced post that I became aware of arara.

What I'm trying to do is also automate the multi-step process of generating a pdf from a music.lytex file.

lilypond-book --output=out --pdf music.lytex 
cd out/
pdflatex music.tex
pdflatex music.tex

I have created the lilypond rule as per the referenced posting (pointed to by araraconfig.yml):

!config
# Mainfile rule for arara
# author: Marco Daniel
# requires arara 3.0+
identifier: lilypond
name: Lilypond
command: <arara> lilypond-book @{format} @{options} @{output} "@{file}"
arguments:
- identifier: format
  flag: <arara> --format=@{parameters.latex-programm}
  default: <arara> --format=latex
- identifier: options
  flag: <arara> @{parameters.options}
- identifier: output
  flag: <arara> --output=@{parameters.output}

I'm hoping for some insight as to whether the rule is correctly configured for the requirements of the task, and how exactly the arara directives should be configured in the lytex file. Currently I have tried variations on:

% arara: lilypond {options: --output=out --pdf music.tex}
% arara: pdflatex: { files: [ out/music.tex ] }

But I am ending up with:

  __ _ _ __ __ _ _ __ __ _ 
 / _` | '__/ _` | '__/ _` |
| (_| | | | (_| | | | (_| |
 \__,_|_|  \__,_|_|  \__,_|

Apparently, there's an invalid directive at line 1. Please take a
look and fix it.

It seems like the word lilypond-book would need to be there in the arara directive, unless that is coming from the rule. I tried removing some of the arguments from the command in the rule.yaml file, but so far my ignorance is winning the argument.

Answer 1

Good news. One of the arara developers helped me solve the problem.

The solution ends up being quiet simple. The only limitation is that we are not outputting the lilypond-book content to a subdirectory as originally planned.

At the top of the music.lytex file (after configuring arara as directed in the referenced post), add the following two directives:

% arara: lilypond: {options: "--pdf"}
% arara: pdflatex: { files: [ 'hymnal.tex' ] }

Now make a file called render.sh containing something like the following:

arara music.lytex
pdflatex music.tex
find . -maxdepth 1 -type d -name '??' -exec rm -rf {} \;
rm *.aux *.bcf *.dep *.out *.run.xml *.tex *.toc tmpx*
open music.pdf

And render and view the resultant pdf file by calling it with bash:

bash render.sh

The middle three lines in the bash script:

pdflatex music.tex

This is because pdflatex needs to be run a second time in order to generate the table of contents.

find . -maxdepth 1 -type d -name '??' -exec rm -rf {} \;

What this line does is remove all of the temporary directories created by the lilypond-book command, which would, if generating into a subdirectory (with the --output=out) flag, be neatly contained in there.

rm *.aux *.bcf *.dep *.out *.run.xml *.tex *.toc tmpx*

All the other temporary files that might interfere with subsequent renderings. NOTE: I may end up deciding (realizing) that the .tex file needs to and can without interference remain.

Thanks, arara crew. Long live the arara bird and Brazilian hospitality!