because they're provided as "default gem" since Ruby 2.6.
We provide "default gem"s as gem ports rather than a part of lang/ruby*
port. files/patch-tool_rbinstall.rb makes not to install such default gems
however hollow wrapper scripts bin/{irb,ri,rdoc} and their manpages were
still left.
This commit intend to move out such wrapper scripts and manpages to gem
ports completely.
PR: 243888
Submitted by: Yasuhiro KIMURA <yasu@utahime.org> (initial revision)
meta (myself)
Differential Revision: https://reviews.freebsd.org/D23514
because racc is provied as "default gem" since Ruby 2.7 [1].
We provide default gems as gem ports rather than a part of lang/ruby* port.
files/patch-tool_rbinstall.rb does that. bin/*racc* are leftover wrapper
script that the patch didn't remove default gem racc completely.
racc is provided by devel/rubygem-racc. To avoid conflict racc gem port vs
ruby port, throw it out completely from ruby port.
[1] https://ruby-trunk-changes.hatenablog.com/entry/ruby_trunk_changes_20190620
PR: 242359 237833
Submitted by: Yasuhiro KIMURA <yasu@utahime.org> (based on)
1. RUBY_PATCHLEVEL has been 0 since Ruby 2.1
2. After RUBY_PATCHLEVEL is removed , RUBY_RELVERSION and RUBY_VERSION are always
same value and it also applies to RUBY_RELEVERSION_CODE and RUBY_VERSION_CODE
3. RUBY_PATCHLEVEL is only used to set value of CPE_UPDATE in lang/ruby2[456] and
setting CPE_UPDATE is optional
4. RUBY_RELEVERSION is only used to set value of CPE_VERSION in lang/ruby2[456]
but as is describled in 2, it can be replased with RUBY_VERSION
5. RUBY_RELVERSION_CODE is not used anywhere
PR: 241473
Submitted by: Yasuhiro KIMURA <yasu@utahime.org>
Reviewed by: sunpoet
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
This resolves a ninja-related issues, corrects passing private args to linker
while building libruby itself (without external LDFLAGS), exports the full
symbols table, and pet 'pkg check -d'. Issues with weechat, vim, facter,
rubygem-hpricot and rubygem-rdiscount should be fixed. See [1] for long story
of hunting and fixing these issues.
Bump PORTREVISIONS accordingly.
PR: 230238 [1], 231361
Submitted by: fuffy
Approved by: fuffy
It was initially got from ruby23, but recent ruby releases have some
differences in runtime linking, which was not hit by exp-run, and caused
trouble with some ports (e.g. devel/leatherman, sysutils/facter).
PR: 230238
Submitted by: fluffy
Reported by: freebsd@ptty.com
Approved by: fluffy
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
lang/ruby23 is already fixed same way, port it to newer releases
By the way, this unbreak ninja builds with any port relied on libruby.so
PR: 229898
Submitted by: fluffy
Reviewed by: ruby (miwi)
Approved by: ruby (miwi)
Exp-run by: antoine
MFH: 2018Q3
Differential Revision: D16341
Since ruby detects this if it's installed, and it's more often installed now
due to other deps, and ruby provides no way to not depend on it if it's found,
pull it in as a dependency unconditionally. While here, fix plist for ruby 2.4
with the CAPIDOCS option on, and restore the MAKE_JOBS_UNSAFE flag when using
that build option since it's not fixed like I thought it was.
PR: 219796
Reported by: Grzegorz Junka <list1@gjunka.com>
