svn commit: r314373 - in head: . etc/defaults etc/rc.d lib/libc/regex share/man/man4/man4.i386 share/man/man5 sys/amd64/conf sys/boot/forth sys/compat/svr4 sys/conf sys/dev/streams sys/i386/conf sy...

[Benjamin Kaduk]

On Tue, Feb 28, 2017 at 3:30 PM, Gleb Smirnoff <glebius at freebsd.org> wrote:

> On Tue, Feb 28, 2017 at 01:39:12PM -0600, Benjamin Kaduk wrote:
> B> > I don't think this deserves UPDATING entry, since it doesn't require
> B> > any action from a person who updates from sources.
> B> >
> B> > I don't think this requires __FreeBSD_version bump, since the latter
> B> > is used to assist compilation of open source application that use
> B> > changed API. The change removed support to run binaries.
> B> >
> B>
> B> That is not the only use of __FreeBSD_version, which is (at least)
> exposed
> B> to the ports collection and can cause conditional changes in what are
> B> shipped by ports.
> B> Which is not to say that any current ports ship affected binaries, of
> B> course, but just to point out that the scope of the symbol is broader
> than
> B> stated.
>
> How can I check the __FreeBSD_version in a port Makefile? My understanding
> is that there is no standard way for such thing. Of course I can parse
> /usr/include/sys/param.h...
>
> My understanding is that the constant is for sources only:
>
> https://www.freebsd.org/doc/en/books/porters-handbook/
> porting-versions.html
>
>
Look for OSVERSION in /usr/ports/Mk/bsd.port.mk

-Ben