Re: a new way to build LilyPond binary releases

[Federico Bruni]

Il giorno ven 13 mar 2020 alle 14:08, Jonas Hahnfeld <address@hidden> 
ha scritto:
> Am Freitag, den 13.03.2020, 13:59 +0100 schrieb Federico Bruni:
> >  Il giorno gio 12 mar 2020 alle 14:39, Jonas Hahnfeld <
> >  address@hidden
> >  >
> >  ha scritto:
> >  > The usage of plain archives has the advantage that the user can
> >  > install
> >  > and move the files anywhere, without invoking any installer. That 
> > is
> >  > by
> >  > design, but maybe there's a valid use case for installers that I'm
> >  > missing? Uninstalling is just as easy as deleting the files (the
> >  > scripts from GUB don't do more than that anyhow).
> >
> >  If you use lilypond with Frescobaldi only, this approach is fine.
> >
> >  But if you want to use it in a terminal, then you have to make some
> >  adjustments: adding the path to PATH for each version installed,...
>
> AFAICT that's not done anymore since 2012: 
> https://github.com/gperciva/gub/commit/917dab12e7a838f1f153e7c57fb921c0b19b9bc2
> So the only thing the installer really does (besides extracting the
> files) is the setup of the .ly extension. Am I missing something else?

Current lilypond installers for Linux will install in /usr/local if run 
as root or IIRC in ~/ if run by the regular user. Additionally, you can 
choose any other directory (e.g. ~/.local) with --prefix option.

So they do not _set_ the path, but just make use of Unix default 
settings.