Subject: Re: __NetBSD_Version__ and stable branches
To: Greg Troxel <firstname.lastname@example.org>
From: Quentin Garnier <email@example.com>
Date: 11/11/2006 15:51:47
Content-Type: text/plain; charset=us-ascii
On Sat, Nov 11, 2006 at 09:22:13AM -0500, Greg Troxel wrote:
> I propose to decouple those two and make __NetBSD_Version__ only an
> indicator of the kernel ABI, completely independent of the version
> reported by "uname -r".
> I think this could be confusing. Your problem is caused, in my view,
> not by the __NetBSD_Version__ value being wrong -- your system did
> indeed change from 3.0 to 3.1, but by the lkm machinery interpreting
> system version number as a kernel ABI version.
> So, perhaps we should introduce __NetBSD_KABI_Version__ and leave it
> at 300000000 on netbsd-3, and keep changing it as we do for current.
> I realize my comments can be viewed as nitpicking over name choices.
> Your proposal of keeping the variable as-is for current and not
> changing it along the stable branch (where KABI changes are
> prohibited) seems very reasonable.
Note that sometimes, __NetBSD_Version__ is used for API versioning,
too. I'd like to see a __NetBSD_KAPI_Version__ also, one that would
Quentin Garnier - firstname.lastname@example.org - cube@NetBSD.org
"You could have made it, spitting out benchmarks
Owe it to yourself not to fail"
Amplifico, Spitting Out Benchmarks, Hometakes Vol. 2, 2005.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (NetBSD)
-----END PGP SIGNATURE-----