Date: Fri, 29 Aug 2014 12:08:59 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 192980] www/squid33 - Wrong option using make config for STRICT_HTTP Message-ID: <bug-192980-13-xtf2p9PfHu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192980-13@https.bugs.freebsd.org/bugzilla/> References: <bug-192980-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192980 --- Comment #21 from John Marino <marino@FreeBSD.org> --- (In reply to Lawrence Chen from comment #20) > But, needing the clarify an option because the prior commit inverted its > behavior, and as a result inverted the previous default build configuration, > is the problem. It means anybody upgrading from squid33 3.3.11_4 or older > may see an unexpected change, it may also stop people from upgrading from > squid32 due to this change. All the squid ports were in terrible, awful shape. I actually doubt many people were using squid32. They'd probably stayed on www/squid or already be on squid33. In any case, it's moot. In 2 weeks anyone on those two ports are going to have to move (or wait until squid34 moves to www/squid soon after). I don't know how serious of an issue this is, but my initial feeling is "not very". Every time the options change, you get the option menu again, so it's not a silent change. Finally, you can't make an omelet without breaking some eggs and that might have happened here. www/squid33 is finally not offensive to took at, it's come a lot way in a couple of days in a group effort. So sorry about the inconvenience, it's to better serve in the future. (think mall construction signs) -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192980-13-xtf2p9PfHu>