Am 28. März 2015 11:51:27 MEZ, schrieb Phil Holmes <m...@philholmes.net>: >----- Original Message ----- >From: "Urs Liska" <u...@openlilylib.org> >To: "Federico Bruni" <fedel...@gmail.com> >Cc: "lilypond-user Mailinglist" <lilypond-user@gnu.org> >Sent: Saturday, March 28, 2015 8:12 AM >Subject: Re: Download link to "current devel" version > > >> Am 28.03.2015 um 07:38 schrieb Federico Bruni: >>> >>> Il 28/mar/2015 07:33 "Federico Bruni" <fedel...@gmail.com >>> <mailto:fedel...@gmail.com>> ha scritto: >>> > >>> > Il 28/mar/2015 02:48 "Urs Liska" <u...@openlilylib.org >>> <mailto:u...@openlilylib.org>> ha scritto: >>> > >>> > > >>> > > Is there a way to point links to the "current development >version" >>> download, i.e. a way to have a link in a program that automatically >>> downloads the current version, without having to manually supply the >>> version? >>> > > >>> > >>> > I'm curious: are you working on a Frescobaldi feature? >>> > >> >> No. As I'm so busy with "das trunkne Lied" and openlilylib at the >moment I >> don't have any capacity to think in that direction. >> >> But of course, if we had a generic way to address the current stable >and >> development version downloads we can use that for letting Frescobaldi > >> install or update LilyPond versions. >> >> Yesterday I realized that I had forgotten to update the LilyPond >version >> in the automated test script we now have for openLilyLib, and that >was >> what made me think about the issue. >> >>> > I can't find anything that you might use here: >>> > http://download.linuxaudio.org/lilypond/binaries/ >>> > >>> > But you can take another approach: use the /development and >/stable >>> alias defined in lilypond.org <http://lilypond.org> htaccess to find >>> "dynamically" the new download links. >>> >>> Oops, forget it. This is true for documentation only. Download pages >are >>> always the same: >>> >>> http://lilypond.org/download.html (stable) >>> http://lilypond.org/development.html (unstable) >>> >>> But I guess that you need a permanent link. It should be asked to >>> linuxaudio.org <http://linuxaudio.org> >> >> OK, I will see what I can get from them. >> >> Best >> Urs > > >Since the installers are all version specific (which I approve of: I >keep >them all separate in a single downloads directory) I don't believe you >can >link to a simple "development installer". You would need to parse the >download pages. >
Ah, OK, that would be possible. However, the most convenient interface would be a generic symlink on linuxaudio that (automatically?) gets updated when new versions are uploaded.. Urs >-- >Phil Holmes _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
