[POLL] need a good name for share/mk API versioning

Ruslan Ermilov · *nix forums addict Joined: 01 Jul 2002 Posts: 65

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
.FreeBSD variable.

Your bet please. I will wait until Monday for poll to settle.

Thanks,
--
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

Mark Valentine · *nix forums addict Joined: 13 Jun 2002 Posts: 62

Ruslan Ermilov · *nix forums addict Joined: 01 Jul 2002 Posts: 65

On Thu, Jul 18, 2002 at 08:43:56PM +0100, Mark Valentine wrote:

M. Warner Losh · *nix forums Guru Joined: 22 Mar 2002 Posts: 365

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

Mark Valentine · *nix forums addict Joined: 13 Jun 2002 Posts: 62

Mark Valentine · *nix forums addict Joined: 13 Jun 2002 Posts: 62

Mark Valentine · *nix forums addict Joined: 13 Jun 2002 Posts: 62

M. Warner Losh · *nix forums Guru Joined: 22 Mar 2002 Posts: 365

In message: <200207201648.g6KGmZJE085462@dotar.thuvia.org>
Mark Valentine <mark@thuvia.demon.co.uk> writes:
: > From: "M. Warner Losh" <imp@bsdimp.com>
: > 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 <mark@thuvia.demon.co.uk> 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

Mark Valentine · *nix forums addict Joined: 13 Jun 2002 Posts: 62

M. Warner Losh · *nix forums Guru Joined: 22 Mar 2002 Posts: 365

In message: <200207201833.g6KIX1FC087737@dotar.thuvia.org>
Mark Valentine <mark@thuvia.demon.co.uk> writes:
: > From: "M. Warner Losh" <imp@bsdimp.com>
: > Date: Sat 20 Jul, 2002
: > Subject: Re: [POLL] need a good name for share/mk API versioning
:
: > 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.
:
: Indeed, if we have __FREEBSD_MK_API_VERSION or equivalent, then ports
: should also use that where appropriate rather than OSVERSION.

Yes. Exactly my point :-)

Warner

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message

Ruslan Ermilov · *nix forums addict Joined: 01 Jul 2002 Posts: 65

On Sat, Jul 20, 2002 at 12:34:56PM -0600, M. Warner Losh wrote:

Google