Re: Updating lilypap, and versions

[Phil Holmes]

----- Original Message ----- 
From: "Graham Percival" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: "Devel" <address@hidden>
Sent: Saturday, April 13, 2013 12:44 AM
Subject: Re: Updating lilypap, and versions


> On Fri, Apr 12, 2013 at 04:25:56PM +0100, Phil Holmes wrote:
> > So
> > I presume the first step to updating lilypad is to create a tarball
> > from github and put it in
> > http://lilypond.org/download/gub-sources/lilypad/.  The slight
> > gotcha alluded to above ("in principle") is that the location
> > specified in the .py config file actually misses out the final
> > /lilypad/, so I'm not sure how it's actually downloaded by GUB.
>
> Hmm.  Tricky.
> https://github.com/gperciva/gub/blob/master/gub/specs/osx-lilypad.py
> clearly has the correct urls, but the windows version at
> https://github.com/gperciva/gub/blob/master/gub/specs/lilypad.py
> doesn't seem to resolve.
>
> What happens if you try a
>  git grep lilypad
> (or maybe something sneakier like "lilypad.*bz2") ?  It's just
> possible that the lilypond-installer builder doesn't use
> gub/specs/lilypad.py.
>
> Also, check your downloads/ directory in gub to see what version
> number of lilypad you have.  Then maybe try changing the url in
> gub/specs/lilypad.py, and see if it fails to download the new
> version?  If you change the url and it complains, then regardless
> of how the original version worked, just upload the new version.

OK.  I created a tarball, uploaded it, changed lilyspec.py and ran bin/gub 
mingw::lilypad - all went well and a new version lilypad has duly been 
created.  I've got a copy on my windows box and it should be in the lilypond 
build due for release this weekend.

Need to update github/GUB now.

> ... actually, now I have a vague recollection of cleaning up the
> gub-sources/ dir by removing tarballs outside of their own proper
> subdirectories.  So maybe GUB only works for you because it
> downloaded that file before I did the cleaning up.
>
> > Anyway - is there a way of managing version numbers?  It looks like
> > we just add one to the 3rd digit in the build whenever it's updated.
> > You think that's true?
>
> That's correct.
>
> UK-bound on Sunday,
> - Graham

Have a good trip.  If you're in East Anglia give me a shout.

--
Phil Holmes