Changes between Version 89 and Version 90 of PortfileRecipes
- Timestamp:
- Oct 14, 2015, 7:27:03 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PortfileRecipes
v89 v90 579 579 580 580 1. Add the `replaced_by` line, indicating the name of the port by which this port has been replaced, for example `replaced_by vineserver`. This causes MacPorts, when running `sudo port upgrade osxvnc`, to deactivate osxvnc and to install vineserver in its place. 581 1. Use the obsolete 1.0 PortGroup. This will take care of things like removing livecheck and giving the user a message stating that the port is indeed obsolete. 581 1. Use the obsolete 1.0 PortGroup. This will take care of things like removing livecheck and giving the user a message stating that the port is indeed obsolete. Note that the `replaced_by` line must precede the `PortGroup obsolete 1.0` line. 582 582 1. In a comment, mention the date, one year in the future, that the port can be removed. 583 583 1. In order for osxvnc to appear in `port outdated`, increase the port's `version`, `revision` or `epoch`. Customarily, the old port's version is set to the version of the replacement port. So, when osxvnc @3.0_1 was replaced by vineserver @3.1_0, osxvnc's `version` was set to 3.1 and its `revision` dropped to 0 to match the new vineserver port. If the software was only renamed, without changing its version number, then increase the old port's `revision`. … … 610 610 611 611 Sometimes a port is replaced because a [ticket:14540 -devel port] was created but will no longer be updated and is being replaced by a corresponding non-devel port. (For example, the xz-devel port was replaced by the xz port.) 612 Ensure that the replacement port does not declare a conflict with the replaced port, as that would prevent the upgrade from succeeding. 612 613 613 614 == Specifying a license == #license