Re: Still failing to operate lilypond 2.20.0 64-bit version.

[Werner LEMBERG]

>> I think it's ghostscript – there are no pre-built packages
>> available either.  While LilyPond doesn't link to it in normal
>> builds, gs is needed for converting LilyPond's EPS output files to
>> PDF.  In other words, a MacPorts user still needs a compiler...
> 
> Damn, you are right. libpaper is listed on
> https://ports.macports.org/port/ghostscript/details/
>
> Well, that's too bad since there is no actual license
> incompatibility due to the use as subprocess, as already noted by
> several others. Not sure if MacPorts can be taught that.

It would be a manual override by the MacPorts people to get pre-built
LilyPond binaries.

However, a better solution to the whole problem is actually quite
simple, providing someone has some experience with MacPorts and a bit
of spare time: Just provide a Pull Request for

  https://trac.macports.org/ticket/66653

to get an LGPLed 'libpaper' library.  It essentially means to clone
the 'macports-ports' repository and change the existing, very small
Portfile at

  https://github.com/macports/macports-ports/blob/master/print/libpaper/Portfile

to use 

  https://github.com/rrthomas/libpaper

instead of the old Debian stuff, also checking and modifying the other
descriptive variables in this file accordingly.

I consider the documentation at https://guide.macports.org/ as quite
good and helpful for writing and testing Portfiles.


    Werner