[Bug 260831] lang/ruby26, lang/ruby27, lang/ruby3[01]: Add DTRACE option

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 16 Jan 2022 23:54:47 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260831

Kubilay Kocak <koobs@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Affects Only Me             |Affects Some People
              Flags|                            |maintainer-feedback?(lab+bs
                   |                            |d@thinkum.space)
            Summary|lang/ruby26, lang/ruby27,   |lang/ruby26, lang/ruby27,
                   |lang/ruby3[01]: patch for   |lang/ruby3[01]: Add DTRACE
                   |making dtrace an optional   |option
                   |feature                     |
           Keywords|                            |needs-patch, needs-qa
             Status|New                         |Open
                 CC|                            |evgeniy@khramtsov.org,
                   |                            |koobs@FreeBSD.org,
                   |                            |lab+bsd@thinkum.space

--- Comment #1 from Kubilay Kocak <koobs@FreeBSD.org> ---
Thank you for the report and patch Sean.

Could you liase with the author of the patches adding DTRACE options in bug
257527 (ruby27) and bug 257525 (ruby26) to produce consolidated patches in
those bugs, as there appear to be some differences.

In particular, check:

 - Whether the configure.ac changes are actually required, and if not, if
--disable-dtrace is insufficient, whether additional configure args/vars can be
set in the Makefile (over patching configure.ac) to ensure the feature is
disabled/enabled deterministically. If we can minimise or remove the need to
patch upstream sources (configure.ac et al), that would be great.

I'll then amend this bug to cover only the ruby3[01] ports once the patches in
this and the other issues are updated.

Alternatively the older issues can be superseded by this one, but this is less
preferred as they have substantial and relevent bug histories.

-- 
You are receiving this mail because:
You are the assignee for the bug.