Graham Percival wrote: > What does this mean? I mean, *any* project would be a problem if > they changed to a non-GPLv2-compatible license. Are they > considering/planning such a change?
Not that I know of. The point is just that most Lilypond dependencies are either called rather than linked to, or have permissive licenses -- (L)GPL'd dependencies like Pango have greater potential for a version upgrade that buggers GPLv2-only code. _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel