From owner-freebsd-arch Fri Jul 19 9: 2:19 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBD8137B400; Fri, 19 Jul 2002 09:02:16 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EE7443E31; Fri, 19 Jul 2002 09:02:15 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.3/8.12.3) with ESMTP id g6JG2C1f031551; Fri, 19 Jul 2002 10:02:13 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 19 Jul 2002 10:01:51 -0600 (MDT) Message-Id: <20020719.100151.96158427.imp@bsdimp.com> To: mark@thuvia.demon.co.uk Cc: ru@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: [POLL] need a good name for share/mk API versioning From: "M. Warner Losh" In-Reply-To: <200207181943.g6IJhu5A016231@dotar.thuvia.org> References: <200207181943.g6IJhu5A016231@dotar.thuvia.org> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <200207181943.g6IJhu5A016231@dotar.thuvia.org> Mark Valentine writes: : > From: ru@freebsd.org (Ruslan Ermilov) : > Date: Thu 18 Jul, 2002 : > Subject: [POLL] need a good name for share/mk API versioning : : > Recently, some backwards incompatible changes were purposedly : > introduced to the share/mk API, particularly to bsd.lib.mk and : > bsd.incs.mk (include files). Everything is OK with src/, but : > some ports/ that rely on FreeBSD's share/mk API should be able : > to use both old (currently in -STABLE, soon to be upgraded to : > the new API) and new versions of the API, so we need to somehow : > differentiate these APIs. The solution is to add the FreeBSD : > specific make(1) variable that could be used to differentiate : > different API versions. : : If this were only for ports, the existing OSVERSION in bsd.port.mk : would suffice, no? No. The OS version and the .mk files may (and often are) unrelated. This is especially true in the case of cross build environments, which are often used to insulate products from whatever version of FreeBSD they happen to be running on. At Timing solutions, we often build 4.5 based products on a 4.3 machine, and vice versa. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message