From owner-freebsd-hackers Tue Jul 1 02:04:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA19883 for hackers-outgoing; Tue, 1 Jul 1997 02:04:01 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19867 for ; Tue, 1 Jul 1997 02:03:56 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id TAA12846; Tue, 1 Jul 1997 19:03:53 +1000 (EST) Message-ID: <19970701190353.50830@rf900.physics.usyd.edu.au> Date: Tue, 1 Jul 1997 19:03:53 +1000 From: David Dawes To: hackers@freebsd.org Subject: Determining FreeBSD versions Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As of X11R6.3, imake parses the output of 'uname -r' to automatically set the OSMajorVersion, OSMinorVersion and OSTeenyVersion parameters. I recently updated a box with 2.1.7.1 to the latest on the RELENG_2_1_0 branch, and as a consequence, 'uname -r' now reports "2.1-STABLE" rather than "2.1.7.1-RELEASE". This results in imake setting OSTeenyVersion to 0 rather than 7, and this does make a difference with the current FreeBSD.cf. 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. David