All ports that previously required ruby 1.8 have either been removed or
been upgraded to use a newer ruby version or no longer depend on ruby
at all.
Our new ruby support policy is to remove the ruby version if nothing
depends on it 6 months after the version moves from general support
to security-only support upstream. This applies to both ruby 2.1 and
2.2 currently, so both are being removed.
OK ajacoutot@, sthen@
security vulnerabilities:
* Fix a DNS request hijacking vulnerability.
* Fix an ANSI escape sequence vulnerability.
* Fix a DOS vulernerability in the query command.
* Fix a vulnerability in the gem installer that allowed a malicious
gem to overwrite arbitrary files.
in rubygems for versions still supported upstream (2.2, 2.3, and 2.4).
No CVE numbers, but this fixes the following vulnerabilities:
* Fix a DNS request hijacking vulnerability.
* Fix an ANSI escape sequence vulnerability.
* Fix a DOS vulernerability in the query command.
* Fix a vulnerability in the gem installer that allowed a malicious
gem to overwrite arbitrary files.
This adds support for FLAVOR=ruby24 to most ruby gem ports, to
allow building of a package for ruby 2.4.
Additionally, refactor ruby.port.mk to reduce duplication and make
future updates simpler.
OK jasper@
This is needed so that the packages do not leave around the directories
when they are removed.
This requires bumping all ruby gem ext ports, which will happen shortly.
Problem discovered by pirofti@
These directories are needed to that installing a ruby gem ext port and
then remove the ruby package doesn't leave directories around. This is
only a partial fix, the ruby gem ext ports all need a similar fix.
Problem pointed out by and feedback from pirofti@
The previous way was bogus. Use bsd.port.arch.mk to remove
MULTI_PACKAGES instead of having the lack of no_* FLAVOR add them.
Change the no_x11 PSUEDO_FLAVOR to no_tk, since what it does is turn
off the -tk subpackage.
Remove post-install target from Makefile.inc, and use a manually
post-install in every version. This is necessary due to
bsd.port.arch.mk usage.
Noticed by tobiasu@
Guidance from espie@