Hack to sysctl kern.osreldate, for ports cluster

Kris Kennaway kris at obsecurity.org
Sat Jan 8 21:58:30 PST 2005

On Sun, Jan 09, 2005 at 06:53:33AM +0100, Michael Nottebrock wrote:
> On Saturday, 8. January 2005 08:13, Craig Rodrigues wrote:
> > Hi,
> >
> >
> > On http://pointyhat.freebsd.org/errorlogs/ it states
> > that sysctl should not be used to determine the
> > version of FreeBSD, and that uname(1) or the OSVERSION
> > variable should be used instead.
> >
> > While a valid thing to do, this is another detail
> > for port maintainers to keep track of.
> How exactly is using sysctl directly less of a 'detail to keep track of' than 
> using the OSVERSION variable provided by bsd.port.mk? I frankly don't see any 
> benefit in being able to call sysctl kern.osreldate from port Makefiles.

Well, some third party software already does, and it can be a bit of
work for me to explain to port maintainers why their port is broken on

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20050108/f8205ed5/attachment.bin

More information about the freebsd-ports mailing list