Is there some way to complain about the treatment one receives when
submitting a valid bug report?
Here is the bug I submitted:
http://bugs.php.net/bug.php?id=36073
The respondent first added the rude comment that is at the bottom of
what you can see on the site and set the status to "Bogus." I then
submitted a follow-up and re-opened the bug. The respondent removed my
additional comments and set the bug status to "Wont fix."
My bug report exists because their is an inconsistency in the PHP
configure process (it behaves one way when configuring for one tool, but
a different way when configuring for another). I provided specific
examples of the inconsistencies. Furthermore, this should be a < 5
minute fix. I even offered to fix the flippin' problem myself!
This sort of response to valid bugs is a large part of why so many of us
have such a hard time selling PHP to our enterprise clients.
Any help that anyone can provide in getting this past the amazingly rude
screener would be appreciated.
Thanks.
My response that was deleted by the respondent follows...
You don't need to be rude:
"Don't try building Mysql yourself if you don't know how to do it
properly."
I have been doing this for many years and know how to do it extremely
well. Don't assume that your bug reporters are all idiots before you
look into it.
I view this as a PHP bug because the PHP configure process looks in the
"lib" directory for other items on an x86_64 system. For example, I
built PostgreSQL from source and used this configure flag in PHP:
--with-pgsql=/usr/local/pgsql
This worked despite the fact that there is no /usr/local/pgsql/lib64 -
which means that their is an inconsistency in the directories into
which the PHP configure process is willing to look between MySQL and
PostgreSQL. If it were consistent in PHP, I would look at it as a
MySQL bug. Since PHP will look into the "lib" directory for other
tools, I can only assume that those responsible for maintaining the
MySQL configure/build process in PHP forgot to include a similar check.
It's a simple check to add.
The fact that I solved the problem and provided enough detail on how to
do so for others should have given you a small clue to the fact that I
do, in fact, know what I am doing.
Responses like you provided are one of the reasons people are reluctant
to provide bug reports.
Please leave this bug report open to see if the configure scripts can't
be changed to look into "lib" as well as the defined libdir for MySQL
the same as it does for other libraries.
If you want or need for me to spend 30 minutes tracking down where the
change needs to be made and exactly what needs to change, I would be
happy to do so over this weekend. My hunch is that the maintainer of
the MySQL code in the PHP configure scripts can locate it in less than
a couple of minutes.
Thanks.
--
Christopher Ostmo
Technology Evangelist,
*STEELHEAD*
[EMAIL PROTECTED]
541.482.6800
spawn || die
