> Howdy all.
>
> I’ve been using macports for a number of years, but have never figured out
> how to readily identify NEW ports (newly available ports, not updates of
> existing packages). I am forced to root around in the ports list or the
> categories among thousands of files, like a pig aft
On Dec 15, 2014, at 5:52 PM, David Wood wrote:
> I’ve been using macports for a number of years, but have never figured out
> how to readily identify NEW ports (newly available ports, not updates of
> existing packages). I am forced to root around in the ports list or the
> categories among t
Under 10.7, 10.8 and 10.9, I was able to install apache2 from ports and point
the OSX server httpd config file to the mod_ssl.so from port and leave the rest
of the settings intact and continue using the Apple supplied httpd and related
files and tools. This allowed me to get the benefits of the
Howdy all.
I’ve been using macports for a number of years, but have never figured out how
to readily identify NEW ports (newly available ports, not updates of existing
packages). I am forced to root around in the ports list or the categories
among thousands of files, like a pig after a shiny,
