Hi.
> On 12/27/15 12:32 PM, "Jacques Menu" wrote:
>>MacPorts as I understand it is meant to work on its own. Since it keeps
>>records of what has been installed, their dependencies and where they
>>have been installed, I don¹t think you can tamper with that easily.
Actually ports in MacPorts dec
On 12/27/15 12:32 PM, "Jacques Menu" wrote:
>Hello Samuel,
>
>MacPorts as I understand it is meant to work on its own. Since it keeps
>records of what has been installed, their dependencies and where they
>have been installed, I don¹t think you can tamper with that easily.
>
>JM
>
>
>> Le 26 dé
Hello Samuel,
MacPorts as I understand it is meant to work on its own. Since it keeps records
of what has been installed, their dependencies and where they have been
installed, I don’t think you can tamper with that easily.
JM
> Le 26 déc. 2015 à 20:57, Br. Samuel Springuel a écrit
> :
>
>
In order to make keeping up with the development version of Lilypond
easier, I'm thinking of transitioning to the MacPorts version (as then
keeping it up to date would automatically be part of my normal MacPorts
maintenance). However, I've noticed that the lilypond-devel port has
dependencies
