On Sun, 24 Apr 2016 09:54:05 +0200 Urs Liska <u...@openlilylib.org> 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 _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
