Date: Wed, 27 Dec 2017 22:32:18 +0800 From: Julian Elischer <julian@freebsd.org> To: Dave Horsfall <dave@horsfall.org>, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Of LSOF Message-ID: <afa77b71-6e3b-c8cb-8249-b11b0b399584@freebsd.org> In-Reply-To: <alpine.BSF.2.21.1712271008040.27626@aneurin.horsfall.org> References: <alpine.BSF.2.21.1712271008040.27626@aneurin.horsfall.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27/12/17 7:14 am, Dave Horsfall wrote: > aneurin# freebsd-version > 10.4-RELEASE-p5 > aneurin# which lsof > /usr/local/sbin/lsof > aneurin# lsof > /dev/null > lsof: WARNING: compiled for FreeBSD release 10.3-RELEASE-p22; this > is 10.4-RELEASE-p3. > aneurin# pkg upgrade lsof > Updating FreeBSD repository catalogue... > FreeBSD repository is up to date. > All repositories are up to date. > Checking integrity... done (0 conflicting) > Your packages are up to date. > aneurin# > > Building it from ports updated it (as I probably did before), but > should not the binary have been updated? Or are binaries not > available for all ports (I guess)? > there is no per release active branch for pkgs, just one for the whole branch. Because we keep binary compatibility we compile for the oldest supported branch. Maybe we should change the test to be less specific, but lsof breaks a lot of rules so maybe it matters more than in other programs.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?afa77b71-6e3b-c8cb-8249-b11b0b399584>