port tries to install already installed packet

[soulne4ny (Alexey Luchko)]

I've faced openssl 1.0.2e compilation issue. ​https://trac.macports.org/ticket/49916 To get around the issue, I decided to install openssl 1.0.2d following ​https://trac.macports.org/wiki/howto/InstallingOlderPort

I've got it installed ` $ port installed openssl The following ports are currently installed:

openssl @1.0.2d_0 (active)

`

But installing anything that depends on openssl, like curl I face an attempt to install the openssl port again. ` $ port install curl ... ---> Computing dependencies for openssl ---> Fetching archive for openssl `

[soulne4ny (Alexey Luchko)]

I've got around it by replacing openssl's Portfile in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/openssl/.

[neverpanic (Clemens Lang)]

This is by design. MacPorts will always attempt to upgrade dependencies of a port first.

In this special case, updating OpenSSL is a very good idea, due to the security fixes the 1.0.2e release has. In the general case, your workaround does not work. Since OpenSSL minor releases are binary-compatible, your workaround is fine for the specific case of OpenSSL. Note that the next selfupdate will likely revert your change to the Portfile.

This is not something we are going to fix. If you want openssl 1.0.2e to build on your system, run sudo port extract openssl, cd to port work openssl, edit the file mentioned in #49916 to explicitly disable addx support and continue by running sudo port upgrade openssl.