>> To build a distributable `mpkg', you have to install MacPorts with
>> a *different* prefix (i.e., not `/opt/local') so that it doesn't
>> interfere with the `standard' MacPorts a user might have installed.
>> And for such custom MacPorts installations only building from
>> source works.
> 
> I made one such distribution, and even sent to a listing of its
> contents, remember?

Ah, ok.  And no, sorry, I don't remember :-)

> I think I put it into /usr/local/lilypond or
> /usr/local/lilypond-devel.  Which location would you prefer?

What about `/opt/lilypond'?

>> [*]: This is essentially a complete re-installation of MacPorts
>>     from scratch, also installing the newest version of XCode and
>>     its command line tools before doing that.
> 
> I am doing that right now, but there are build errors.

More or less expected; at least, this is my impression reading the
macports mailing list.  It will take some weeks until all rough edges
are fixed in Catalina support.


    Werner

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to