Date: Sun, 5 Sep 2010 19:00:23 GMT From: Garrett Wollman <wollman@FreeBSD.org> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/150235: sysutils/smartmontools build system bug Message-ID: <201009051900.o85J0Nxr072364@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/150235; it has been noted by GNATS. From: Garrett Wollman <wollman@FreeBSD.org> To: Alex Samorukov <samm@os2.kiev.ua> Cc: bug-followup@FreeBSD.org, developers@FreeBSD.org Subject: Re: ports/150235: sysutils/smartmontools build system bug Date: Sun, 5 Sep 2010 14:53:10 -0400 <<On Sun, 05 Sep 2010 20:24:59 +0200, Alex Samorukov <samm@os2.kiev.ua> said: > Very funny. I don`t think so. Try to argue your position next time, > this may help. Only if someone is willing to actually engage in an argument. > BTW - this "bug" was in smartmontools from early beginning and only > you hit this condition - i think that is very good indicator of its > importance, isn`t it? A bug is a bug. > Your commit will break smartmontools functionality, as i mentioned > before. Thats why i`m against it. Try to read before posting. What commit? I haven't committed anything. > The required file was never included in the /usr/include. And it was > changed more then once from the beginning. If anything in userland links against a kernel header, then that header needs to be installed in /usr/include, end of story. -I/usr/src/sys is never acceptable in userland code. > You can troll this way as long as you want. And of course, you VERY need > to upgrade smartmontools in the middle of the system upgrade cycle. Of course one needs to upgrade all ports in the middle of the upgrade cycle, if one wishes to have a working system at the end of it -- particularly in the case of something that uses CAMIOCOMMAND, which does not have any backwards-compatibility mechanism (hmmm, another bug here). -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201009051900.o85J0Nxr072364>