> On Sep 23, 2016, at 09:41, William H. Magill wrote:
>
> I have two systems, an iMac and a Mac Mini.
> The iMac doesn’t do much - mostly aspell, and so my update to Sierra went
> quite smoothly.
>
> The Mac Mini on the other hand, is a bit more of a workhorse. Primarily
>
Hi,
I would suggest in your case, because your port list might be a little
out of date, to not use the ./restore_ports.tcl scripts. Instead,
manually look at your myports.txt and requested.txt files, decide which
ports you still want and try install them one by one, with whatever
variants
I have two systems, an iMac and a Mac Mini.
The iMac doesn’t do much - mostly aspell, and so my update to Sierra went quite
smoothly.
The Mac Mini on the other hand, is a bit more of a workhorse. Primarily acting
as a web server.
And, as I updated to Sierra, I discovered to my chagrin that I
Hi. After I upgraded to MacPorts 1.4, I noticed that freetype is now
at 2.3.2, where the version I have installed is 2.1.10.
I would like to upgrade to the latest version, but I also have
several ports installed that depend on freetype. How do I know if
2.3.2 is binary compatible with
On Apr 6, 2007, at 02:08, Nathan Brazil wrote:
Hi. After I upgraded to MacPorts 1.4, I noticed that freetype is
now at 2.3.2, where the version I have installed is 2.1.10.
freetype 2.3.2 would have been available to previous MacPorts
versions as well through a simple port sync.
I would
Citando Ryan Schmidt :
On Apr 6, 2007, at 02:08, Nathan Brazil wrote:
Hi. After I upgraded to MacPorts 1.4, I noticed that freetype is
now at 2.3.2, where the version I have installed is 2.1.10.
freetype 2.3.2 would have been available to previous MacPorts
versions as well through