Up to [cvs.NetBSD.org] / pkgsrc / devel / ruby-byebug
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
devel/ruby-byebug: update to 13.0.0 pkgsrc change: remove Ruby version restriction. 13.0.0 (2026-01-15) Fixed * #924: Use typed data APIs to fix Ruby 4.0 deprecation (@nobu). * #876: Add explicit require of stringio (@pabloh). * #909: Avoid loading readline at all to play nice with Ruby 4.0. * #905: Make reline an explicit dependency to fix Ruby 3.4 warnings. * #824: Improve startup by loading IRB lazily (@pocke). * #848: Grammar fixes in GUIDE.md (@alexymik). * #804: Fix typo in context.rb documentation (@ono-max). Removed * Support for MRI 3.1. Byebug no longer installs on this platform.
Drop support for Ruby 3.1
devel/ruby-byebug: update to 12.0.0 12.0.0 (2025-03-25) Changed * #690: break without any arguments now sets a breakpoint on the current line, just like gdb (@sergioro9). Fixed * #741: Small consistency issues in help messages. * #743: untracevar command crashing when giving a non existent global variable. * #744: Another punctuation tweak in enable breakpoints help message. * #736: Skip warning about $SAFE global variable on ruby 2.7 when listing global variables. Added * #847 and #850: Support for MRI 3.1, 3.2, and 3.3 (@marshall-lee). * #688: where command now receives an optional numeric argument <n> to print the nth first frames (@sergioro9). Removed * Support for MRI 2.4, 2.5, 2.6, 2.7 and 3.0. Byebug no longer installs on this platform.
devel/ruby-byebug: fix for ruby33 Depends on devel/ruby-readline prior to ruby33.
devel/ruby-byebug: update to 11.1.3 Update ruby-byebug to 11.1.3. ## [11.1.3] - 2020-04-23 ### Fixed * [#674](https://github.com/deivid-rodriguez/byebug/pull/674): crash when using byebug on ruby 2.7.0 on Windows. ## [11.1.2] - 2020-04-17 ### Fixed * [#657](https://github.com/deivid-rodriguez/byebug/pull/657): crash when hitting \<TAB\> due to IRB completion mechanism included in the default ruby 2.7 version of the `irb` gem ([@terceiro]).
devel/ruby-byebug: update to 11.1.1 Update ruby-byebug to 11.1.1. ## [11.1.1] - 2020-01-24 ### Fixed * [#635](https://github.com/deivid-rodriguez/byebug/pull/635): usage on Fedora 31 or any other `byebug` installation performed by a `rubygems` copy customized by setting `Gem.install_extension_in_lib` to false.
devel/ruby-byebug: update to 11.1.0 Update ruby-byebug to 11.1.0. ## [11.1.0] - 2020-01-20 ### Added * Official support for MRI 2.7 ([@yui-knk]). ### Fixed * [#562](https://github.com/deivid-rodriguez/byebug/pull/562): post mortem mode landing in the wrong line when coming from an exception inside a `Kernel.load` call. ### Removed * Support for MRI 2.3. Byebug no longer installs on this platform.
devel/ruby-byebug: update to 11.0.1 ## [11.0.1] - 2019-03-18 ### Fixed * [#546](https://github.com/deivid-rodriguez/byebug/pull/546): `continue!` to ignore further `byebug` calls. * [#545](https://github.com/deivid-rodriguez/byebug/pull/545): `skip` autolisting code for intermediate skipped breakpoints.
devel/ruby-byebug: update to 11.0.0 ## [11.0.0] - 2019-02-15 ### Added * [#377](https://github.com/deivid-rodriguez/byebug/pull/377): `skip` to continue until the next breakpoint as long as it is different from the current one. You can use this command to get out of loops, for example ([@tacnoman]). * [#524](https://github.com/deivid-rodriguez/byebug/pull/524): `continue!` (or `continue unconditionally`) to continue until the end of the program regardless of the currently enabled breakpoints ([@tacnoman]). ### Fixed * [#527](https://github.com/deivid-rodriguez/byebug/pull/527): `break` help text to clarify placeholders from literals. * [#528](https://github.com/deivid-rodriguez/byebug/pull/528): `quit!` help to not show a space between "quit" and "!". ### Removed * Support for MRI 2.2. Byebug no longer installs on this platform.
devel/ruby-byebug: update to 10.0.2 ## 10.0.2 - 2018-03-30 * Error when using byebug with `debase` gem (#447, @tzmfreedom)
devel/ruby-byebug: update to 10.0.1 ## 10.0.1 - 2018-03-21 ### Fixed * Error when using byebug with `debase` gem (#443, @tzmfreedom)
devel/ruby-byebug: update to 10.0.0 10.0.0 - 2018-01-26 Changed * Breaking on methods now stops on the first effective line of a method, not on the line containing the def keyword. Added * Show valid breakpoint locations when invalid location given (#393, @ko1). * Ruby 2.5.0 support (#397, @yui-knk). * Log host & port when launching byebug's client in remote mode. * Some love & tests to remote debugging (#82). * remote_byebug shortcut to start the most common case for remote debugging (#141). Fixed * Properly ignore ruby fullpath executable when passed to byebug script (#419). * Remote server crash when interrupting client (#141, #274). * Control server thread being able to interrupt main thread only a single time. (#239).
Update ruby-byebug to 9.1.0. ## 9.1.0 - 2016-08-22 ### Added * Better UI messages for breakpoint management. ### Fixed * `where` command failing on instance_exec block stack frames. * `restart` command crashing in certain cases because of a missing `require 'English'` (#321, @akaneko3). * `restart` command crashing when debugged script is not executable or has no shebang (#321, @akaneko3). ### Removed * Ruby 2.0 and Ruby 2.1 official & unofficial support. Byebug no longer installs on these platforms.
Switch github HOMEPAGEs to https.
Add ruby-byebug package version 9.0.6. Byebug is a simple to use, feature rich debugger for Ruby 2. It uses the new TracePoint API for execution control and the new Debug Inspector API for call stack navigation, so it doesn't depend on internal core sources. It's developed as a C extension, so it's fast. And it has a full test suite so it's reliable. It allows you to see what is going on _inside_ a Ruby program while it executes and offers many of the traditional debugging features such as: * Stepping: Running your program one line at a time. * Breaking: Pausing the program at some event or specified instruction, to examine the current state. * Evaluating: Basic REPL functionality, although [pry] does a better job at that. * Tracking: Keeping track of the different values of your variables or the different lines executed by your program.