Re: MacOS release help

On Tue, 2022-10-18 at 10:44 -0600, Carl Sorensen wrote: > On Tue, Oct 18, 2022 at 9:58 AM Jean Abou Samra > 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 > > >

Re: MacOS release help

On Mon, 2022-10-17 at 17:05 -0600, Carl Sorensen wrote: > On Mon, Oct 17, 2022 at 3:49 PM Alex Harker > wrote: > > If I’m not correct about an installer then I don’t understand what > > kind of app you were referring to when you said: > > > > > The other point that was raised in the past was pack

Re: MacOS release help

On Mon, 2022-10-17 at 22:26 +0100, Alex Harker wrote: > Apologies for retreading old ground - I was unaware that this was the > case and I’ve obviously misunderstood what you were getting at > earlier in the thread entirely. Imistook the comments about a > Lilypond app and dmg earlier to mean LilyP

Re: MacOS release help

Hi all, > I am starting to think that since Frescobaldi is the most complete > and beginner-friendly LilyPond environment out there, having a good > installing experience for Frescobaldi and LilyPond together would make > the installing experience for LilyPond without Frescobaldi much less > relev

Re: MacOS release help

On Tue, Oct 18, 2022 at 9:58 AM Jean Abou Samra 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

Re: MacOS release help

I agree strongly with this, yes On Tue, 18 Oct 2022, 18:14 Jean Abou Samra, wrote: > Le 18/10/2022 à 08:12, Alex Harker a écrit : > > > > > >> On 18 Oct 2022, at 00:05, Carl Sorensen > >> wrote: > >> > >> IMO, what we most want is an app bundle that can be easily relocated > >> anywhere and tha

Re: MacOS release help

Le 18/10/2022 à 08:12, Alex Harker a écrit : On 18 Oct 2022, at 00:05, Carl Sorensen wrote: IMO, what we most want is an app bundle that can be easily relocated anywhere and that provides all of the binaries used by LilyPond.  Frescobaldi can be pointed at that app bundle to run LilyPond.

Re: MacOS release help

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.

Re: MacOS release help

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 a

Re: MacOS release help

> On 18 Oct 2022, at 00:05, Carl Sorensen wrote: > > IMO, what we most want is an app bundle that can be easily relocated anywhere > and that provides all of the binaries used by LilyPond. Frescobaldi can be > pointed at that app bundle to run LilyPond. > > I recognize that most apps have

Re: MacOS release help

Hi Carl, > IMO, what we most want is an app bundle that can be easily relocated > anywhere and that provides all of the binaries used by LilyPond. > Frescobaldi can be pointed at that app bundle to run LilyPond. That sounds great to me! > In my opinion, we want to have > a) an installer for Fres

Re: MacOS release help

On Mon, Oct 17, 2022 at 3:49 PM Alex Harker wrote: > This is a continuation of the discussion from lilypond-u...@gnu.org > in a more appropriate place. > > I’m responding to Jean and Jonas together as the two most recent sets of > comments were strongly related. > >

MacOS release help

This is a continuation of the discussion from lilypond-u...@gnu.org in a more appropriate place. I’m responding to Jean and Jonas together as the two most recent sets of comments were strongly related. > On 17 Oct 2022, at 20:33, Jean Abou Samra wrote: > > I was