My trick to having a harmonious multi-package manager system is to have a
hierarchy, in which MacPorts is where the majority of packages are built,
and the others are only used to fill in the gaps.
For example, Free Pascal. MacPorts doesn't have it. I could spend the time
creating a port, but I
You replied only to me. Remember to use the Reply All button in your email
program to reply to the group also. I’ve re-added the group address to this
reply.
On Feb 12, 2014, at 01:37, macosforge.99.ky...@spamgourmet.com wrote:
Thank you for responding to my query（not sure if this reply is
On Feb 9, 2014, at 23:15, Nick Wharton nick.p.whar...@gmail.com wrote:
I'm on Mavericks trying to get mapserv running from the cgi-bin directory
under the Apache root. The server is up and responding to http://127.0.0.1
but http://127.0.0.1/cgi-bin/mapserv is popping up a Safari dialog This
It's possible to get Fink and MacPorts to work together, although I don't
recommend it. Before we had ROOT in MacPorts, my wife and I got this to
work on her machine for Particle Physics-y things. Homebrew however, does
not really work and play well with others. If you want to use it, you
really
I understand why installing in /usr/local can mess up macports, but macports
doesn't have everything, and most third-party software wants to go into
/usr/local. Where should this stuff go, if not /usr/local?
Greg Shenaut
___
macports-users mailing
On Wed, Feb 12, 2014 at 10:04 AM, Gregory Shenaut gkshen...@ucdavis.edu wrote:
I understand why installing in /usr/local can mess up macports, but macports
doesn't have everything, and most third-party software wants to go into
/usr/local. Where should this stuff go, if not /usr/local?
I
I understand why installing in /usr/local can mess up macports, but
macports doesn't have everything, and most third-party software wants to go
into /usr/local. Where should this stuff go, if not /usr/local?
Actually, I don't think there is that much of a problem with installing
software in
Hi,
Actually, I don't think there is that much of a problem with installing
software in /usr/local, the problem is the particular way that Homebrew does
it by default, taking over /usr/local completely, and it's disregard for
standard ownership and permissions.
You're wrong on that one. The
--On February 13, 2014 1:24:57 AM +0100 Clemens Lang c...@macports.org
wrote:
If those binary installers did install headers in /usr/local/include
and libraries in /usr/local/lib that has been pure luck. As soon as
you install a port that has an optional dependency not installed via
MacPorts
They've really started to run into the same problems that MacPorts solved
long ago. Considering the their page title is Homebrew -- MacPorts driving
you to drink? Try Homebrew!, I find pleasure in their difficulty. The only
thing I wish we did that they do is git. But we don't forbid it, so eh.
On Feb 12, 2014, at 18:24, Clemens Lang wrote:
export MANPATH=/opt/local/share/man:${MANPATH}
export INFOPATH=/opt/local/share/info:${INFOPATH}
As far as I know those aren't used on newer versions of OS X and are
automatically derived from the value of $PATH.
As far as I know they are
On Feb 12, 2014, at 18:46, Mike Alexander wrote:
--On February 13, 2014 1:24:57 AM +0100 Clemens Lang wrote:
If those binary installers did install headers in /usr/local/include
and libraries in /usr/local/lib that has been pure luck. As soon as
you install a port that has an optional
12 matches
Mail list logo
