Hey all,
i wanted to upgrade git-core by:
$ sudo port upgrade git-core
and get :
--- Activating git-core 1.5.3.1_0+doc
Error: Activating git-core 1.5.3.1_0 failed: Image error: Another version of
this port (git-core @1.5.0.5_0) is already active.
the I deactivated it :
$ sudo port deactivate
On Jun 12, 2008, at 09:43, Yvon Thoraval wrote:
i wanted to upgrade git-core by:
$ sudo port upgrade git-core
and get :
--- Activating git-core 1.5.3.1_0+doc
Error: Activating git-core 1.5.3.1_0 failed: Image error: Another
version of this port (git-core @1.5.0.5_0) is already active.
I just got around to upgrading my work machine to leopard. The first
problem I ran into was that apparently I had a really old xcode
installed, so none of the old ported binaries would run (something about
an old threading model no longer supported apparently). I upgraded that
and did the
On Jun 12, 2008, at 15:52, Alan Batie wrote:
I just got around to upgrading my work machine to leopard. The
first problem I ran into was that apparently I had a really old
xcode installed, so none of the old ported binaries would run
(something about an old threading model no longer
On Jun 11, 2008, at 17:59, Watson Ladd wrote:
Ryan Schmidt wrote:
On Jun 11, 2008, at 14:53, Ralph Pass wrote:
Ryan Schmidt wrote:
What entities could MacPorts have?
macboats?
macships?
maccanoes?
macdocks?
macpallets?
macboxes?
maccrates?
:-)))
I just knew this was coming. :)
Ryan Schmidt wrote:
Ort has the added advantage (or possibly confusion) that it's just
one letter off from port...
sudo ort install
MacOrts
This rather looks like a typo to me :-)
Rainer
___
macports-users mailing list
Ryan Schmidt wrote:
For these reasons you may be better off uninstalling MacPorts and then
reinstalling the ports you need.
!!!
Consider this a feature request that port upgrade actually do an
upgrade... I realize that's a different sort of upgrade, but this is
going to be a royal pain in
Alan Batie wrote:
Consider this a feature request that port upgrade actually do an
upgrade... I realize that's a different sort of upgrade, but this is
going to be a royal pain in the backside...
MacPorts simply cannot know that the underlying platform changed. But
this does not happen
Ryan Schmidt wrote:
One way to improve this would be to remove autoselected variants during
upgrade if they aren't applicable anymore. For example, if you have a
port installed with +darwin_8 but you're now on Leopard, upgrading the
port should deselect the darwin_8 variant.
Can you think
On 12Jun2008 17:27, Alan Batie [EMAIL PROTECTED] wrote:
Ryan Schmidt wrote:
One way to improve this would be to remove autoselected variants during
upgrade if they aren't applicable anymore. For example, if you have a
port installed with +darwin_8 but you're now on Leopard, upgrading the
Cameron Simpson wrote:
Breaking cycles doesn't turn it into a tree, but fortunately that's ok;
an acyclic digraph is fine - you can traverse it like a tree and just
need to avoid rebuilding a package you rebuilt on another path. Which
macports seems to do just fine anyway.
If it looks like a
Cameron Simpson wrote:
Gentoo's emerge has a --pretend mode that is very useful. Does port
install have that?
There's a somewhat bitrotted patch here:
http://trac.macports.org/ticket/11892
- Josh
___
macports-users mailing list
12 matches
Mail list logo
