[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Static URLs pointing to releases
From: |
Urs Liska |
Subject: |
Re: Static URLs pointing to releases |
Date: |
Fri, 10 Mar 2017 10:26:04 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0 |
Hi Phil,
thank you for pushing me in the right direction.
Of course that's possible. I'll have to use website/unix.html etc. but
these do give me the required information. And
http://download.linuxaudio.org/lilypond/binaries/freebsd-64/ and friends
provide the links to all available binaries. I thought I couldn't "glob"
a URL like http://download.linuxaudio.org/lilypond/binaries/freebsd-64/*
to get all available files but the index page *does* include all links.
Best
Urs
Am 10.03.2017 um 10:16 schrieb Phil Holmes:
> ----- Original Message ----- From: "Urs Liska" <address@hidden>
> To: "lilypond-devel" <address@hidden>
> Sent: Friday, March 10, 2017 8:39 AM
> Subject: Static URLs pointing to releases
>
>
>> This had come up at some point, but I don't think we came to a
>> conclusion, so ...
>>
>> Is it possible to have static URLs somewhere at lilypond.org that point
>> to the binaries of the latest stable and latest development releases?
>>
>> The idea is for a script or program to be able to automatically retrieve
>> these binaries without a user having to manually specify them.
>>
>> Use cases are: arbitrary scripts, Frescobaldi, (openLilyLib) automated
>> testing.
>>
>> There should either be URLs for all provided versions or generic URLs
>> from which the link to a specific OS version can be generated.
>>
>> An alternative would be a, say, JSON file with the URLs for *all*
>> available binaries, not only the respective "latest". I'm sure there
>> would be people around who'd appreciate the ability to choose arbitrary
>> versions from a Frescobaldi-generated dropdown list.
>>
>> Any ideas?
>
> Strictly speaking, there are static URLs that point at the binaries:
> http://lilypond.org/website/download.html for the stable and
> http://lilypond.org/website/development.html for the development.
> Shouldn't be too hard to parse those to get the locations of the
> binaries themselves?
>
> --
> Phil Holmes
--
address@hidden
https://openlilylib.org
http://lilypondblog.org