From owner-freebsd-arch Thu Jul 18 11: 5:13 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 92FB837B400 for ; Thu, 18 Jul 2002 11:05:07 -0700 (PDT) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AA3743E31 for ; Thu, 18 Jul 2002 11:05:04 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g6II50b71736 for arch@FreeBSD.org; Thu, 18 Jul 2002 21:05:00 +0300 (EEST) (envelope-from ru) Date: Thu, 18 Jul 2002 21:05:00 +0300 From: Ruslan Ermilov To: arch@FreeBSD.org Subject: [POLL] need a good name for share/mk API versioning Message-ID: <20020718180500.GC63636@sunbay.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eRtJSFbw+EEWtPj3" Content-Disposition: inline User-Agent: Mutt/1.3.99i 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 --eRtJSFbw+EEWtPj3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! 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. So I would like to run a short pool as to what the name of this variable should be (the draft is _FREEBSD_MK_API_VERSION), and what should be its numbering scheme. I would like this numbering scheme to be a monotonically increasing natural number. This would be good because the same numbering scheme would be used in both -STABLE and -CURRENT, and would be bad because specific backwards incompatible API changes should be merged in the same order as they were applied to -CURRENT. The variable must be put into sys.mk (so that it's always defined), and one option it to use an already existing =2EFreeBSD variable. Your bet please. I will wait until Monday for poll to settle. Thanks, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --eRtJSFbw+EEWtPj3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9NwNMUkv4P6juNwoRAkNRAJ4wO5eDpG9vz9RhOZDXMB8Lxdh+nQCfZQT7 fpCwLeeaEmn5b7tZ4C++33k= =rFKZ -----END PGP SIGNATURE----- --eRtJSFbw+EEWtPj3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message