Subject: Re: Check for "test ... == ..." in configure scripts
To: None <firstname.lastname@example.org>
From: David Howland <email@example.com>
Date: 10/17/2006 14:04:30
I havn't been following the reason for these changes very closely. I'm
sure these changes weren't made without good reason. I have no doubt
the intentions were good. BUT...
net/kismet is now broken on my netbsd 3.1 system. It will not
configure. All I had to do to get it to build properly was to re-add
the "==" that the new patches had removed in favor of "=". Once the
tests were returned to normal, the package built fine. Were these
changes tested at all before they were imported? Perhaps they work on
4.0, I dont know, but this sure gave me a real "WTF?" moment today.