rocky/rpms — comment on commit 84ad492450de5d34a89356189ea0c75884966270
File: specs/bashdb/bashdb.spec line 12
By rocky:

The release name needs a little explanation.

The releasename contains the target (and initial) version of bash that the debugger works off; the release name also contains the version for the debugger.

As many times as not, a newer version of bash will break bashdb. When that happens, the next bashdb release has an updated version number in the bash portion of the release name.

So for example bashdb-3.1-0.08 works with bash 3.1 and bash 3.2.
bashdb-3.1-0.09 works with the same versions of bash, but the debugger was updated; hence the 0.08 to 0.09 change.

bashdb-4.0-0.1 works with bash 4 and greater. It's possible bashdb-3.1-0.09 works with bash 4, but bashdb-4.0-0.1 has bug fixes and new features that bashdb-3.1-0.09 doesn't.

One more quirk bashdb-4.2-0.8 does work on bashdb-4.1. I developed it on bash 4.2 which is why the 4.2 release number. Sometime after release I relized it would work on 4.1 which is the latest RHEL and CENTOS version.