[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Download link to "current devel" version
From: |
Urs Liska |
Subject: |
Re: Download link to "current devel" version |
Date: |
Sat, 28 Mar 2015 12:32:41 +0100 |
User-agent: |
K-9 Mail for Android |
Am 28. März 2015 11:51:27 MEZ, schrieb Phil Holmes <address@hidden>:
>----- Original Message -----
>From: "Urs Liska" <address@hidden>
>To: "Federico Bruni" <address@hidden>
>Cc: "lilypond-user Mailinglist" <address@hidden>
>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" <address@hidden
>>> <mailto:address@hidden>> ha scritto:
>>> >
>>> > Il 28/mar/2015 02:48 "Urs Liska" <address@hidden
>>> <mailto:address@hidden>> 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
- Download link to "current devel" version, Urs Liska, 2015/03/27
- Re: Download link to "current devel" version, Federico Bruni, 2015/03/28
- Re: Download link to "current devel" version, Federico Bruni, 2015/03/28
- Re: Download link to "current devel" version, Urs Liska, 2015/03/28
- Re: Download link to "current devel" version, Phil Holmes, 2015/03/28
- Re: Download link to "current devel" version,
Urs Liska <=
- Re: Download link to "current devel" version, Phil Holmes, 2015/03/28
- Re: Download link to "current devel" version, Urs Liska, 2015/03/28
- Re: Download link to "current devel" version, Phil Holmes, 2015/03/28
- Re: Download link to "current devel" version, Jim Long, 2015/03/29
- Re: Download link to "current devel" version, Jim Long, 2015/03/29
- Re: Download link to "current devel" version, Urs Liska, 2015/03/29