Date: Fri, 19 Jul 2002 10:01:51 -0600 (MDT) From: "M. Warner Losh" <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 Message-ID: <20020719.100151.96158427.imp@bsdimp.com> In-Reply-To: <200207181943.g6IJhu5A016231@dotar.thuvia.org> References: <mailpost.1027015694.14024@thuvia.demon.co.uk> <200207181943.g6IJhu5A016231@dotar.thuvia.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200207181943.g6IJhu5A016231@dotar.thuvia.org>
Mark Valentine <mark@thuvia.demon.co.uk> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020719.100151.96158427.imp>