[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ANN: Frescobaldi 2.19.0
From: |
Johan Vromans |
Subject: |
Re: ANN: Frescobaldi 2.19.0 |
Date: |
Sun, 24 Apr 2016 10:12:36 +0200 |
On Sun, 24 Apr 2016 09:54:05 +0200
Urs Liska <address@hidden> wrote:
> If you install LilyPond through your (Linux) OS's package manager this
> will detect any updates to the OS's packages (of course) and will
> therefore update automatically whenever you run your package manager's
> update procedure (e.g. apt-get update && upat-get upgrade).
> If you have downloaded LilyPond as a binary release this will of course
> *not* detect the availability of any newer releases.
Much simpler: Frescobaldi seems to use the timestamp of the binary to detect
updates.
My lilypond binary is ~/bin/lilypond, which basically
execs /usr/bin/lilypond with some additional --include paths.
When /usr/bin/lilypond is updated to a newer version, this is not detected
since the timestamp of ~/bin/lilypond doesn't change.
As remarked by Villum: detecting newer versions is efectively
"circumvented somehow in the setup".
> So *now* Frescobaldi does detect updates on the
> LilyPond side, that is, when you have updated LilyPond outside of
> Frescobaldi.
*now* being > 2.19.0 ?
-- Johan
- Re: ANN: Frescobaldi 2.19.0, (continued)
Re: ANN: Frescobaldi 2.19.0, Federico Bruni, 2016/04/23
Re: ANN: Frescobaldi 2.19.0, Davide Liessi, 2016/04/23
Re: ANN: Frescobaldi 2.19.0, Steve Noland, 2016/04/22
Re: ANN: Frescobaldi 2.19.0, Villum Sejersen, 2016/04/24