Issue #2331 has been updated by Sergio Gelato.
Nigel Kersten wrote:
> I wonder how many people are running versions of MacPorts that are this
> old... still, it would be good if we could pinpoint exactly when this
> behaviour changed.
The MacPorts ChangeLog mentions the following:
------------------------------------------------------------------------
r46052 | [email protected] | 2009-01-28 02:32:11 +0100 (Wed, 28 Jan 2009) |
2 lines
Error out when asked to upgrade a port that is not installed, e.g. the
infamous "port upgrade all"
------------------------------------------------------------------------
This first appeared in the 1.7.1 release.
A more interesting question, to which I don't have an answer, is how far back
one has to go to find a release where "port install" cannot be used. Do we even
know that that was the reason for trying to use "port upgrade" always (as
opposed to the well-known programmer's virtue called laziness)?
----------------------------------------
Bug #2331: darwinports "install" broken
http://projects.puppetlabs.com/issues/2331
Author: asa hammond
Status: Accepted
Priority: High
Assignee: Nigel Kersten
Category: OSX
Target version: 0.25.6
Affected version: 0.25.1
Keywords: darwinports, macports
Branch:
looks like the darwinport provider is not able to "install" on osx leopard.
ports tries "port update" instead of "port install" when first installing a
package. Seems that macports Version: 1.710 has this issue.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
