The idea is to be able to install libs & tools related to lilypond, and use them without too much hassle.
Dependencies for a project are declared in a filename called Lypadfile
packages are Ruby gems, downloadable using the gem tool.
package names are prefixed with lypad-. That way we can tell which gems are lypad-related. For example, a package called lilyjazz will be published as a gem called lypad-lilyjazz.
system is ruby based.
lypad command line tool is basically a wrapper around gem / bundler.
lypad also provides some lib tools for stuff like installing fonts, or changing the stock lilypond installation in any way.
When Lypad is installed it modifies lilypond to add a few lilypond commands used to reference and load packages.
Loading packages in lilypond sources
\require "lilyjazz" % that's all folks
Command line interface
lypad update # updates the lypad installation and installs hooks in the current lilypond installation
lypad install # installs anything in Lypadfile
lypad install <gem> # installs the gem
lypad install <gem> -s # installs the gem and writes it to Lypadfile
lypad uninstall <gem>
lypad list # lists all lilypond-related gems
noteflakes
commented
8 years ago
The idea is to be able to install libs & tools related to lilypond, and use them without too much hassle.
lypad-. That way we can tell which gems are lypad-related. For example, a package calledlilyjazzwill be published as a gem calledlypad-lilyjazz.When Lypad is installed it modifies lilypond to add a few lilypond commands used to reference and load packages.
Loading packages in lilypond sources
Command line interface