From owner-freebsd-hackers  Tue Jul  1 05:44:11 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id FAA27837
          for hackers-outgoing; Tue, 1 Jul 1997 05:44:11 -0700 (PDT)
Received: from bitbox.follo.net (eivind@bitbox.follo.net [194.198.43.36])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA27830
          for <hackers@FreeBSD.ORG>; Tue, 1 Jul 1997 05:44:08 -0700 (PDT)
Received: (from eivind@localhost) by bitbox.follo.net (8.8.5/8.7.3) id OAA14341; Tue, 1 Jul 1997 14:43:43 +0200 (MET DST)
Date: Tue, 1 Jul 1997 14:43:43 +0200 (MET DST)
Message-Id: <199707011243.OAA14341@bitbox.follo.net>
From: Eivind Eklund <perhaps@yes.no>
To: David Dawes <dawes@rf900.physics.usyd.edu.au>
CC: hackers@FreeBSD.ORG
In-reply-to: David Dawes's message of Tue, 1 Jul 1997 19:03:53 +1000
Subject: Re: Determining FreeBSD versions
References: <19970701190353.50830@rf900.physics.usyd.edu.au>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Is there a better way to reliably distinguish between versions,
> particularly the vintage of one of the "-STABLE" versions?  The imake
> config allows these version parameters to be manually overriden, and
> that's what I'm doing for now.  It would be good if the auto-detect
> mechanism could be made to work in this case though.  I don't mind so
> much about -CURRENT, since that's known to be more of a moving target.

/usr/include/osreldate.h should be fairly easy to parse, and give very
good data, especially after the format was fixed :)

Eivind.