simon-git: gonville (master): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  35a5707 Complete rework of the distribution archive system.

Repository:     https://git.tartarus.org/simon/gonville.git
On the web:     https://git.tartarus.org/?p=simon/gonville.git
Branch updated: master
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2020-03-21 09:38:06

commit 35a570732773174aa0b169fe1822f6d051a33dfc
web diff https://git.tartarus.org/?p=simon/gonville.git;a=commitdiff;h=35a570732773174aa0b169fe1822f6d051a33dfc;hp=9be29ca4b8aed9df598d371366d32bb5fc530eb7
Author: Simon Tatham <anakin at pobox.com>
Date:   Sat Mar 21 09:23:52 2020 +0000

    Complete rework of the distribution archive system.
    
    I noticed a week or so ago that you could _almost_ get Lilypond to use
    Gonville _without_ having to install it in LILYPOND_DATADIR, simply by
    using the -I option to add the directory containing my font files to
    the include path. However, when I tried it, a few glyphs didn't come
    out in Gonville: time signatures and dynamics came out in DejaVuSans
    instead.
    
    Now I've found out why, and how you can fix it: it's because Lilypond
    displays those glyphs using Pango rather than manual 'glyphshow' or
    equivalent, so Pango needs to have the font available on _its_ path.
    Luckily, there's a function exposed in the Lilypond Guile layer that I
    can simply call in gonville.ily which will do that.
    
    So now you don't have to do any cumbersome installation at all: if you
    have Lilypond 2.20, you can set an existing score in Gonville just by
    unpacking my tarball and running Lilypond with two extra command-line
    options (an -I, and a -d include-settings to include gonville.ly).
    
    That's so convenient that I've changed my mind completely about how I
    want the distribution archive to look! This change reworks the build
    scripts and READMEs so that we now build completely separate archives
    for use with Lilypond before and after 2.20. The 'after' archive is
    much simpler, and although it still does say _something_ about
    installing Gonville in the Lilypond data dir, it's strictly optional -
    there's no longer any need to do it at all, it's just that you can do
    it if you want to avoid having to type that tedious -I every time.
    
    Also, in this commit, I've removed the nasty use of 'unshare' in
    Buildscr, because now I've found out that you can use Gonville without
    having to install anything anywhere, why wouldn't I do it myself?

 Buildscr         |  50 +++++++++++---------------
 README           |  97 --------------------------------------------------
 README.post-2.20 | 106 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 README.pre-2.20  |  75 +++++++++++++++++++++++++++++++++++++++
 demo.sh          |  18 ++++++++++
 glyphs.py        |  25 ++++++++-----
 gonville.ily     |   8 +++++
 7 files changed, 243 insertions(+), 136 deletions(-)