Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Discard OpenBSD release number in config[:os] #1905

wants to merge 1 commit into from

2 participants


The rationale for this is as follows.

OpenBSD has a continuous evolution release model. The release numbers change twice a year like clockwork and reflect the release process phases rather than revolutionary changes of the platform (which are intentionally kept to a minimum). The system probably doesn't change radically enough to merit a release number in the os name here. OpenBSD is OpenBSD.

Notice also that the release number does not follow the major/minor convention, for obvious reasons. Release 5.0 was simply the next release after 4.9.


What issues are caused by having the number?


I'm sure no serious issues are involved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Sep 16, 2012
  1. @tonysidaway
This page is out of date. Refresh to see the latest.
Showing with 1 addition and 0 deletions.
  1. +1 −0  configure
1  configure
@@ -28,6 +28,7 @@ class Configure
@host = `sh -c ./rakelib/config.guess`.chomp
/([^-]+)-([^-]+)-(.*)/ =~ @host
@cpu, @vendor, @os = $1, $2, $3
+ @os.sub! /openbsd[0-9\.]*$/, "openbsd" # Discard OpenBSD version number
@little_endian = false
@sizeof = {}
Something went wrong with that request. Please try again.