FreeBSD Ports

Update to 6.57. Changes: https://metacpan.org/changes/distribution/Mojolicious

graphics/zimg: conflict with graphics/sekrit-twc-zimg

graphics/zimg: conflict with graphics/sekrit-twc-zimg

Update to 0.26. Depend on just vim, not ${LOCALBASE}/bin/vim. Add TEST_DEPENDS, NO_ARCH, and sort plist. PR: 207893 Approved by: maintainer timeout (> 3 weeks)

security/l5: modernize port a bit - replace EXTRACT_SUFX with USES equivalent - use modern way of defining BROKEN to avoid using of bsd.port.pre.mk No functional changes, so no PORTREVISION bump is required.

Only pull in p5-Scalar-List-Utils if the XS option is turned on, as it was before r412231. PORTREVISION bump for default dependency change.

Mark BROKEN: tries to download from registry.npmjs.org during stage phase npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "/wrkdirs/usr/ports/misc/teslams/work/teslams-6f6dfa2" npm ERR! node v5.9.1 npm ERR! npm v2.14.7 npm ERR! ... [More] code EAI_FAIL npm ERR! errno EAI_FAIL npm ERR! syscall getaddrinfo npm ERR! network getaddrinfo EAI_FAIL registry.npmjs.org:443 Reported by: pkg-fallout MFH: 2016Q2 [Less]

Update to 5.9p1. Notable changes: * The rtable option was removed from server and servers. Users of "server * rtable X" will need to switch to launching ntpd with # setfib -F X /usr/sbin/ntpd * Various improvements to the HTTPS constraint ... [More] feature (requires LibreSSL). This port reenables rtable support in the listen option on FreeBSD. Relnotes: http://www.openntpd.org/txt/release-5.9p1.txt [Less]

During the exp-run in bug 208158, it was found that www/node gives errors with libc++ 3.8.0 [1]: /usr/include/c++/v1/map:837:5: error: static_assert failed "Allocator::value_type must be same type as value_type" static_assert((is_same::value), ... [More] ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../deps/v8/src/compiler/js-type-feedback.h:41:21: note: in instantiation of template class 'std::__1::map, v8::internal::zone_allocator >' requested here TypeFeedbackIdMap type_feedback_id_map_; ^ This is because libc++ 3.8.0 has added these sanity checks for custom std::map allocators, which *must* be of the type std::pair. I fixed the few std::map instances in the node source by adding this to their allocator types. Approved by: [email protected] (maintainer) PR: 208270 MFH: 2016Q2 [Less]

Update to 1.2.0