Besides whereas Frescobaldi is a Lilypond editor (thereby requires is and depends on it), Lilypond is not a Frescobaldi compiler, they're not dependent in the other direction. So the Lilypond installer shouldn't know about Frescobaldi
Further, a package with no GUI elements doesn't bump me at all. The thing to do would be to insoect how similar tools are distributed (gcc, clang, web servers, ftp servers this kind of "service" stuff) and draw inspiration from those L On Tue, 18 Oct 2022, 17:59 Jean Abou Samra, <j...@abou-samra.fr> wrote: > Le 18/10/2022 à 01:05, Carl Sorensen a écrit : > > In my opinion, we want to have > > a) an installer for Frescobaldi that could install LilyPond if > > desired, and > > b) an installer for LilyPond that could install Frescobaldi if desired. > > > Why would we need both? I think a) is the most sensible, because all > Frescobaldi users need LilyPond, while not all LilyPond users need > Frescobaldi. > > > Jean > >
