From owner-freebsd-current Thu Oct 29 09:16:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18586 for freebsd-current-outgoing; Thu, 29 Oct 1998 09:16:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18581 for ; Thu, 29 Oct 1998 09:16:46 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id JAA04055; Thu, 29 Oct 1998 09:16:24 -0800 (PST) (envelope-from jdp) Message-Id: <199810291716.JAA04055@austin.polstra.com> To: "Andrey A. Chernov" cc: current@FreeBSD.ORG Subject: Re: FreeBSD_cc_... In-reply-to: Your message of "Thu, 29 Oct 1998 10:06:40 +0300." <19981029100640.A13026@nagual.pp.ru> Date: Thu, 29 Oct 1998 09:16:24 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We already do a similar thing with and __FreeBSD_version. > > Not so similar because _we_ control version numbering scheme for us. > > > I think it's pretty unlikely that GNU will release a version with a > > 5-component revision number. > > Consider following alternatives: > > 2.72.1 > 2.7.2.1 > 2.721 > 27.2.1 > > and so on - they will be the same in your check. > > The main point is that GNU version numbering scheme is out of our control, > so we can assume _anything_ can happens there. Yes, I see your point. I'll change it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message