Date: Wed, 30 Oct 2013 14:34:20 -0400 From: Zaphod Beeblebrox <zbeeble@gmail.com> To: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Two interesting things that broke in the package system while I wasn't looking. Message-ID: <CACpH0MdubxqAxZMMLY1n6eSwOmmwyZRf=_ad0emEawRviR0E-A@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
The life-cycle of a machine often runs something like: - Machine gets installed/configured/put online for a purpose. - Someone pays attention for awihle. - It largely gets ignored - Then something breaks - Then someone has to pay attention Recently, I have encountered a hassle with a bunch of 7.2 machines that need upgrading. Two things, really, that are broken. I realize that 7.2 isn't supported... but these two things are errors that don't need to be errors --- it's just sloppy. The first is the code that recognizes a library is installed. I don't know where this is, but it recently changed s.t. it gives an error on 7.2 machines. Looks like sloppy shell code that doesn't work on 7.2's /bin/sh. The second is pkg itself. Not especially needed on 7.2, but one little check instead of just OS is FreeBSD for posix_fallocate(), is should be OS is FreeBSD _and_ OS_VERSION > something. I'm not sure what version posix_fallocate(0 appeared ... but that should be there.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACpH0MdubxqAxZMMLY1n6eSwOmmwyZRf=_ad0emEawRviR0E-A>