Date: Sun, 9 Jan 2005 06:53:33 +0100 From: Michael Nottebrock <michaelnottebrock@gmx.net> To: freebsd-ports@freebsd.org Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: Hack to sysctl kern.osreldate, for ports cluster Message-ID: <200501090653.37252.michaelnottebrock@gmx.net> In-Reply-To: <20050108071324.GA32371@crodrigues.org> References: <20050108071324.GA32371@crodrigues.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1542904.r9f48pVSnc Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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' th= an=20 using the OSVERSION variable provided by bsd.port.mk? I frankly don't see a= ny=20 benefit in being able to call sysctl kern.osreldate from port Makefiles. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1542904.r9f48pVSnc Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB4MbhXhc68WspdLARAgYDAKCfmViN6MqP/NH1ycB5ZWb1+wQYNwCgh2AS Lg0lceSjZMcAeDqKZpyEodA= =NWkY -----END PGP SIGNATURE----- --nextPart1542904.r9f48pVSnc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501090653.37252.michaelnottebrock>