The semi-offical lyp package index

Editorial tools

• edition-engraver - Editorial tweaking for Lilypond.

Fonts

• beethoven - Beethoven font package.
• bravura - Bravura SMuFL font for Lilypond.
• gootville - Gootville SMuFL font for Lilypond (based on Gonville).
• haydn - Haydn font package.
• improviso - Improviso font package.
• lilyjazz - LilyJazz font package.
• paganini - Paganini font package.
• profondo - Profondo font package (a non-SMuFL Bravura clone).
• smufl - Support for SMuFL fonts.

Frameworks

• structure - A framework for writing big scores in Lilypond (WIP).

Harmony

• microlily - Microtonal support for Lilypond.
• roman-numerals - A package for roman numeral harmonic analysis.

Instrument-specific notation

• chtab - Alternative TabStaff algorithm.
• lilydrum - Right-left drum notation (mainly for pipeband snare drumming).

OpenLilyLib

• oll-core - Basic functionality for OpenLilyLib packages.
• oll-ji - Commands for notating music in just notation.

Special notation

• frame-engraver - Engrave boxes around notes (for modern notation).
• pedal-decorations - Pedal mark decorations for Lilypond.
• slashed-beams - Slashed beams for Lilypond.

Support Libraries

• assert - Assertions for Lilypond packages.
• lys - Run Lilypond as a server.
• svg-metadata - Add metadata to SVG output.

Tweaking

• auto-extenders - Automatic lyrics line extenders for Lilypond.
• merge-rests - Rest merging engraver.
• super-shape-me - Slur & tie tweaking for Lilypond.

Contributing

This repository contains a YAML index of Lilypond packages that can be installed using lyp, the Lilypond package manager.

To add your package to the index:

1. Fork this repository
2. Add your package to index.yml under the packages, using the following format:

packages:
  <package-name>:
    url: <public git url>
    description: <short description>
    author: <author>

3. Add your package to this README file under the proper section (or possibly create a new section).
4. Submit a pull request

The rules

1. The package name must be unique, the packages in the index file should be ordered alphabetically.
2. The git url could be a github repository id (i.e. userid/mypackage), a partially-qualified URL (i.e. acme.com/myrepo.git), or a fully-qualified URL (i.e. https://github.com/blah/blah.git)
3. The package should include a package.ly file in its root directory. This is the entry point for the package.
4. Additional .ly files can be included using relative \includes.
5. The package should have a README and include a license, either as part of the code, in the README, or in a separate file.
6. Transitive dependencies are defined as usual using \require.
7. The package repository should be versioned using git tags. Version tags can be optionally prefixed with v (for example v0.2).
8. Including the package in the index is optional. It allows users to install your package using a short unique name, but your package could always be installed using its publicly-accessible git URL.