On 2014-02-12, at 3:50 PM, Art McGee wrote:
On a related note, Homebrew is actually based on GNU Stow. It's basically a
clone/ripoff with enhancements. If you're going to use Homebrew, then use it
in the same way suggested for Stow, and install packages in your home
directory, leaving
On Feb 13, 2014, at 8:07PM, asllearner wrote:
Sterling Smith wrote
According to
https://trac.macports.org/wiki/FAQ#usrlocal
you could try to rename /usr/local. MacPorts doesn't install anything to
/usr/local. If there is anything that stops working, then try to install
it from
I also install into /opt/something where something expands to something
descriptive of all the crap I am installing in there. Then I can turn PATHs
on and off depending. This is really important for playing with things like
the gtk+ cocoa that needs its whole space to itself. Just DONT use /opt or
On Feb 14, 2014, at 08:46 , Mark Anderson e...@emer.net wrote:
I also install into /opt/something where something expands to something
descriptive of all the crap I am installing in there. Then I can turn PATHs
on and off depending. This is really important for playing with things like
the
On Feb 14, 2014, at 11:56, Gregory Shenaut wrote:
On Feb 14, 2014, at 08:46 , Mark Anderson wrote:
I also install into /opt/something where something expands to something
descriptive of all the crap I am installing in there. Then I can turn PATHs
on and off depending. This is really
On Fri, Feb 14, 2014 at 12:56 PM, Gregory Shenaut gkshen...@ucdavis.eduwrote:
I've been reluctant to use anything under /opt because in the event I ever
need to scrub macports and start over, it's easier to remove /opt and
reinstall macports from scratch.
Other third party software uses /opt
Hi,
So let's be a little more specific. You are saying that it's
/usr/local/include and /usr/local/lib that are the problem, not
/usr/local/bin, right? Otherwise you're saying that, for example,
MacPorts is incompatible with BBEdit (which puts symlinks in
/usr/local/bin). Very few
directly, since it wasn't on the list
archive when I loaded it) so all should be well, though of course, now
my original message has divided in th
http://mac-os-forge.2317878.n4.nabble.com/Re-Where-should-non-macports-sw-be-installed-Was-Problem-with-Macports-homebrew-and-ghostscript-tt243935.html
and active. What
would be the difference? How would this impact mapcports?
--
View this message in context:
http://mac-os-forge.2317878.n4.nabble.com/Problem-with-Macports-homebrew-and-ghostscript-tp243740p244031.html
Sent from the MacPorts - Users mailing list archive at Nabble.com
of removing
brew.
The link talks about temporarily renaming usr/local while installing ports,
i.e. if installation of a port runs into conflicts with usr/local. That is
not quite my problem...
--
View this message in context:
http://mac-os-forge.2317878.n4.nabble.com/Problem-with-Macports-homebrew
using the homebrew version now be able to find it in
macports, or is that magical thinking?
--
View this message in context:
http://mac-os-forge.2317878.n4.nabble.com/Problem-with-Macports-homebrew-and-ghostscript-tp243740p244033.html
Sent from the MacPorts - Users mailing list archive
-os-forge.2317878.n4.nabble.com/Problem-with-Macports-homebrew-and-ghostscript-tp243740p244034.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.
___
macports-users mailing list
macports-users@lists.macosforge.org
https
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
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
(I apologize if this message appears more than once; I haven't used the list in
a long time, and I had some problem figuring out how I set it up the first
time. I have tried a few times to post, but it has failed to appear...I think I
was using the right address this time, though I also tried
Based on some bad internet advice I appear to have installed homebrew
without realizing it is not compatible (so to speak) with macports, and so
I installed ghostscript via homebrew, without realizing that I had already
installed it via macports, and that it appears to have been already
Adding the list.
On Feb 11, 2014, at 4:55AM, Sterling Smith wrote:
Fellow User,
According to
https://trac.macports.org/wiki/FAQ#usrlocal
you could try to rename /usr/local. MacPorts doesn't install anything to
/usr/local. If there is anything that stops working, then try to
You might want to rebuild your ports to ensure they did not link against
/usr/local.
This probably works for this purpose:
sudo mv /usr/local{,-moved-for-macports}
port echo installed port-installed.txt
port echo requested and active port-requested-active.txt
sudo port -f uninstall installed
On Tue, Feb 11, 2014 at 4:12 PM, Art McGee amc...@gmail.com wrote:
They keep their environment segregated from the rest of the system, and
because of this, even though any MacPorts admin will strongly and
vehemently advise against even trying it, they can work in concert with
each other.
Hi,
You might want to rebuild your ports to ensure they did not link against
/usr/local.
This probably works for this purpose:
sudo mv /usr/local{,-moved-for-macports}
port echo installed port-installed.txt
port echo requested and active port-requested-active.txt
sudo port -f uninstall
Sending again from the correct address…
On Feb 11, 2014, at 03:08, macosforge.99.ky...@spamgourmet.com wrote:
Based on some bad internet advice I appear to have installed homebrew without
realizing it is not compatible (so to speak) with macports, and so I
installed ghostscript via
30 matches
Mail list logo
