From owner-freebsd-arch Sat Jul 20 11:14:52 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 600FE37B401; Sat, 20 Jul 2002 11:14:49 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C952F43E31; Sat, 20 Jul 2002 11:14:47 -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 g6KIEk1f040124; Sat, 20 Jul 2002 12:14:46 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 20 Jul 2002 12:14:07 -0600 (MDT) Message-Id: <20020720.121407.17240249.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: <200207201648.g6KGmZJE085462@dotar.thuvia.org> References: <20020719.100151.96158427.imp@bsdimp.com> <200207201648.g6KGmZJE085462@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: <200207201648.g6KGmZJE085462@dotar.thuvia.org> Mark Valentine writes: : > From: "M. Warner Losh" : > Date: Fri 19 Jul, 2002 : > Subject: Re: [POLL] need a good name for share/mk API versioning : : > In message: <200207181943.g6IJhu5A016231@dotar.thuvia.org> : > Mark Valentine writes: : > : 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. : : Does this work for the ports system? I recognise the need for cross builds, : but didn't consider it for ports. After all, they already use OSVERSION... Using OSVERSION may be sufficient for the ports. Using a __FREEBSD_MK_API_VERSION variable would also be sufficient, as well as allowing for people that use the bsd.*.mk files externally to the project to continue to do so and cope with the different APIs. I've not looked at porting out .mk files over to the new scheme, so I don't know how necessary this would be. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message