Created attachment 175125 [details] Proposed patch (since 415658 revision) Patch to update www/aria2 port from 1.23.0 to 1.27.1 version. Look following link for changes: https://github.com/aria2/aria2/compare/release-1.23.0...release-1.27.1 - Adapt MASTER_SITES - Add SSH2 option - USES+=ssl instead of USE_OPENSSL=yes The build tested on FreeBSD 10.2 amd64.
A commit references this bug: Author: jbeich Date: Mon Oct 17 04:34:34 UTC 2016 New revision: 424093 URL: https://svnweb.freebsd.org/changeset/ports/424093 Log: www/aria2: update to 1.28.0 - Expose SSH2 option (appeared in 1.19.0) - Chase HTTP redirect in MASTER_SITES - Convert USE_OPENSSL=yes into USES+=ssl Changes: https://github.com/aria2/aria2/compare/release-1.23.0...release-1.28.0 Changes: https://github.com/aria2/aria2/releases PR: 212960 Submitted by: lightside@gmx.com Approved by: maintainer timeout (3 weeks) Changes: head/www/aria2/Makefile head/www/aria2/distinfo
@sunpoet, As a fellow maintainer I can guess why --enable-libaria2[1] is in CONFIGURE_ARGS unconditionally but not why other --{en,dis}able-* and --with{,out}-* aren't exposed via OPTIONS_DEFINE. Digging through history these explicit switches started to accumulate since ports r173659. Even in those dark times OPTIONS existed, so if you have a rationale don't time out. SSH2 option landed as is, probably breaking statu quo. [1] to not break dependencies but such switches can often be split between slave ports
(In reply to comment #2) > SSH2 option landed as is, probably breaking statu quo. The libssh2.so dependency was found by stage-qa, because of [default=check] in configure script. Therefore, I added it as configurable option. Possible to change defaults on discretion of maintainer. As I understood, previously it wasn't detected, because of no libssh2.so dependency to check on build cluster for this port. Thanks for commit and update to latest version.