How to upgrade a port's version locally

Updating macports on mac

Sometimes a port is replaced because a -devel port was created but will no longer be updated and is being replaced by a corresponding non-devel port. See the next section below for instructions on how to choose just the fortran compiler based on gcc variants. For software whose developers habitually stealth-update their software, further measures may need to be taken, such as those employed by the dcraw and molden ports. If these files are of value to the end user, they should be installed by the port in the post-destroot phase.

When other ports are updated this can cause issues when the newer version of a port is needed for compatibility. Instead, rely on the information cached in the port index. It's iterpreted as list, though. Until ticket is implemented, proper handling of these config files must be done for each port. See also the next entry on unversioned distfiles.

If you fail to use the correct capitalization, the port may still install on your system, but will fail for users with case-sensitive filesystems. If the software was only renamed, without changing its version number, then increase the old port's revision. Yet it still tries to build universal because it got the universal -arch flags from libetpan's config script, so the build fails. Ensure that the replacement port does not declare a conflict with the replaced port, as that would prevent the upgrade from succeeding.

Be sure to return to this window after every Xcode upgrade to ensure that the command line tools are also upgraded. Unversioned distfiles Although they would be wise not to do this, some software developers may distribute their distfile with a filename that does not contain the version number e. The current solution is to rename any config files to append a.

Customarily, the old port's version is set to the version of the replacement port. So the stub port should not be deleted until after most users can be expected to have used sudo port selfupdate and sudo port upgrade outdated. This usually means you already have the latest version installed. Otherwise, the port will be installed with the latest version specified. If the installation of a port fails, you should always clean and try again, i.

These outcomes are bad since it loses what the user updated. Since you're already in the directory containing the Portfile, you can also open it directly from here, but port edit always works. So that users will see the update, the revision is increased, but users who already have the previous distfile would then experience a checksum mismatch.

Yet it still tries to

See UsingTheRightCompiler for a list of available compiler values. Similarly, if the Portfile has a livecheck section which uses livecheck. If a variant depends on or conflicts with other variants, a line detailing that follows. See Invoking Port Variants below to install ports that have variants.

If the software was

Without the deactivate hack the activation phase of port B would fail because one of the files it tries to install is already there. Note that Apple might at some point discontinue providing these updates via their update servers. It is better to make a user upgrade to a newer Xcode than for a port maintainer to spend time testing old versions. Compare the old distfile with the new one. In order for osxvnc to appear in port outdated, increase the port's version, revision or epoch.

It is, however, much faster. It's up to the user to issue the correct command and to the port maintainer to check for the installed variant.

Its libetpan-config script contains -arch flags. In these cases you can use configure. See also the previous entry on stealth updates. Note The installation of a single port consists of multiple phases. Sometimes the new distfile does not differ materially from the old one e.

If you fail to use the

If it doesn't succeed, that goes beyond the scope of this document. The second argument is a version number, which in this case we leave empty.

The deactivate hack works around this problem, by deactivating A if it is active. While are derived from the variants. Variants are a way for port authors to provide options you can use to customize your build at install time. The port's checksums then need to be updated, but the version stays the same e. Dependencies are the packages are required by a port at runtime library and runtime dependencies or required to install it build, fetch, and extract dependencies.