Re: lilypond 2.19.80

[Ricardo Wurmus <rekado@elephly.net>]

Hi Mason,

> If it's simple enough for me to understand and you can briefly explain
> how I'd be happy to do it now and as needed in the future.

Great!  I appreciate the initiative.

First, you need to have a copy of the Guix sources.  I recommend
following the documentation here:

    http://www.gnu.org/software/guix/manual/html_node/Contributing.html

It boils down to getting the sources via git, and then building them
in an environment spawned by “guix environment guix”.

Once that’s out of the way, you can edit the lilypond package definition
either by opening “gnu/packages/music.scm” and searching for
“define-public lilypond”, or by running “./pre-inst-env guix edit
lilypond”.

You’ll see that the version string would need to be changed from
"2.19.63" to "2.19.80".  Another string that needs to be changed is the
hash, i.e. the bit of gibberish in “(sha256 (base32 …))”.  To compute
the hash follow these steps:

    wget https://download.linuxaudio.org/lilypond/source/v2.19/lilypond-2.19.80.tar.gz
    guix hash lilypond-2.19.80.tar.gz

This command will print the new hash string.  Just replace the existing
hash with that new string.

Save the file and make a git commit with these commands:

    export EDITOR=nano  # or whatever your favourite editor is
    git add gnu/packages/music.scm
    git commit

This will open up your editor and prompt you for a message.  Here’s an
appropriate commit message for this change:

--8<---------------cut here---------------start------------->8---
gnu: lilypond: Update to 2.19.80.

* gnu/packages/music.scm (lilypond): Update to 2.19.80.
--8<---------------cut here---------------end--------------->8---

When you save and exit the editor, git will record the commit.  You can
then tell git to format the last commit as a patch with “git
format-patch -1” and send the resulting file to guix-patches@gnu.org via
email.

Hope this helps!

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net