On Thu, May 16, 2019 at 6:22 PM David Kastrup <d...@gnu.org> wrote: > Marnen Laibow-Koser <mar...@marnen.org> writes: > > > On Thu, May 16, 2019 at 5:01 PM David Kastrup <d...@gnu.org> wrote: > > > >> marnen <mar...@marnen.org> writes: > >> > >> > My understanding from other posts here (correct me if I'm wrong) is > >> > that a major (legal, not technical) roadblock for doing this with GUB > >> > is the licensing requirement that seems to require that Xcode be run > >> > on Apple hardware, and the lack of consistent availability of Apple > >> > hardware for builds. > >> > >> The GPL 3.0 does not allow additional restrictions such as requiring > >> certain hardware. Availability is not an issue, the restrictions are. > >> > > [...] > > > > Xcode is not governed by GPL3, and AFAIK it's the only component at issue > > here whose license stipulates particular hardware. > > GUB is governed by the GPLv3. Nobody claims that people may not > independently create ports of LilyPond for MacOSX but creating them as > part of GUB in the general release process is not an option with the > current Xcode license.
Perhaps I don’t understand. If GUB merely calls out to Xcode, how is this a GPL3 issue? > > -- > David Kastrup > -- Marnen Laibow-Koser mar...@marnen.org http://www.marnen.org Sent from Gmail Mobile _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
