[MacPorts] #52101: openssl @1.0.2h_1: update to 1.1.1

[MacPorts]

#52101: openssl @1.0.2h_1: update to 1.1.1
----------------------+--------------------
  Reporter:  larryv   |      Owner:  larryv
      Type:  update   |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:
Resolution:           |   Keywords:
      Port:  openssl  |
----------------------+--------------------

Comment (by FranklinYu):

 Replying to [comment:21 yan12125]:
 > Some old software will never get OpenSSL 1.1 compatibility as they have
 been dropped upstream before OpenSSL 1.1.0 is released. Examples are
 Python 2.x < 2.7 and 3.x < 3.5 (1). If MacPorts switches to OpenSSL 1.1,
 what to do with those ports? IMO backporting is not an option for old
 Python versions as the patch is quite big.
 >
 > In Arch Linux, OpenSSL 1.0 and 1.1 co-exist, and old packages are built
 against OpenSSL 1.0. An issue in such an approach is that OpenSSL 1.0
 should be built with versioned symbols (2) so that there are no conflicts
 if a program (directly or indirectly) links to both OpenSSL 1.0 and 1.1.
 I'm not sure if it's a problem or not in macOS/Mach-O.
 >
 > (1) https://bugs.python.org/issue26470
 >
 > (2)
 https://git.archlinux.org/svntogit/packages.git/tree/trunk/openssl-1.0
 -versioned-symbols.patch?h=packages/openssl-1.0

 Would it be feasible to release a Port revision for all the affected
 ports?

-- 
Ticket URL: <https://trac.macports.org/ticket/52101#comment:27>
MacPorts <https://www.macports.org/>
Ports system for macOS