ports/security/rubygem-net-ssh, branch 2017Q2FreeBSD ports treehttps://cgit-dev.freebsd.org/ports/atom?h=2017Q22017-02-20T15:10:22ZUpdate to 4.1.02017-02-20T15:10:22ZSunpoet Po-Chuan Hsiehsunpoet@FreeBSD.org2017-02-20T15:10:22Zurn:sha1:fd7d24b14c8970aa158f8101eea8d938058089d2
Changes: https://github.com/net-ssh/net-ssh/blob/master/CHANGES.txt
security/rubygem-net-ssh: update to 4.0.12017-01-09T02:28:30ZSteve Willsswills@FreeBSD.org2017-01-09T02:28:30Zurn:sha1:dd952ea5f1ae92a9e59e2db255686c93c6ac6cb6security/rubygem-net-ssh: update to 4.0.02016-12-28T16:31:05ZSteve Willsswills@FreeBSD.org2016-12-28T16:31:05Zurn:sha1:e55ace52fecea433ad84b9260d3e0c2056117ae2Convert USES=gem:autoplist to USES=gem since autoplist is default2016-04-27T21:57:31ZSteve Willsswills@FreeBSD.org2016-04-27T21:57:31Zurn:sha1:462519941e56e838fd1fff77ecc3ebeb554fcb80create USES=gem and update rubygem- ports to use it2016-04-27T16:36:41ZSteve Willsswills@FreeBSD.org2016-04-27T16:36:41Zurn:sha1:b3e8fe8d85d1f32b6b8813589ed8637a8accb185
Note that for now ports still have to have USE_RUBY=yes to use USES=gem
PR: 209041
Differential Revision: https://reviews.freebsd.org/D6070
Remove ${PORTSDIR}/ from dependencies, categories r, s, t, and u.2016-04-01T14:25:16ZMathieu Arnoldmat@FreeBSD.org2016-04-01T14:25:16Zurn:sha1:597afc47baba19000afd8ec4880a2c47975b0367
With hat: portmgr
Sponsored by: Absolight
- Update to 3.1.12016-03-25T20:03:41ZSunpoet Po-Chuan Hsiehsunpoet@FreeBSD.org2016-03-25T20:03:41Zurn:sha1:d116ae4aa43aa1714cb75523469ca9138bf5d97a
- Add LICENSE_FILE
- Remove outdated PORTSCOUT
Changes: https://github.com/net-ssh/net-ssh/blob/3-1-release/CHANGES.txt
- Update to 3.1.02016-03-20T18:38:38ZSunpoet Po-Chuan Hsiehsunpoet@FreeBSD.org2016-03-20T18:38:38Zurn:sha1:702e53eb24d9d3d4a186ad6434b21e85d6ee5a22
Changes: https://github.com/net-ssh/net-ssh/blob/master/CHANGES.txt
- Update to 3.0.22016-01-16T18:11:23ZMartin Wilkemiwi@FreeBSD.org2016-01-16T18:11:23Zurn:sha1:4293187f7277b8adc6ff8a9b065c12471d086066
PR: 206130
Submitted by: Torsten Zuehlsdorff
Remove UNIQUENAME and LATEST_LINK.2015-08-17T14:20:40ZMathieu Arnoldmat@FreeBSD.org2015-08-17T14:20:40Zurn:sha1:21a283f3bec444388d1448f993783ec673a06502
UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.
Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.
Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)
Reviewed by: antoine, bapt
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D3336