Date: Sun, 11 Sep 2005 07:50:14 -0700 From: Vizion <vizion@vizion.occoxmail.com> To: Alex Dupre <ale@FreeBSD.org> Cc: Giorgos Keramidas <keramida@ceid.upatras.gr>, freebsd-questions@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: php extensions compile error - another compile bug? Message-ID: <200509110750.15613.vizion@vizion.occoxmail.com> In-Reply-To: <4323EA55.2030708@FreeBSD.org> References: <200509090959.40296.vizion@vizion.occoxmail.com> <200509091848.53844.vizion@vizion.occoxmail.com> <4323EA55.2030708@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 11 September 2005 01:27, the author Alex Dupre contributed to the dialogue on- Re: php extensions compile error - another compile bug?: >Vizion wrote: >> Getting near the end and I get this: >> ---------------------------------------------- >> >> I do not know whether you have time to look at this one or not? > >I have no time to look at this because you are spamming my and other >email addresses and mailing lists with dozen of messages. Seeing as I am in the process of trying to build a resource to help victims of the Katrina disaster your tone of correspondence, and speed of engagement, has the unfortunate effect of reminding me about FEMA. There are two bugs in the makefile and one other issue that causes problems, so it is not surprising that some degree of traffic was generated. Seeing as the two bugs appear to be in your php Makefile and that other people have helped me resolve them on the mailing lists, it is not surprising you have received, not only the private email, but also the listmail which tracked how others responded, while you sat back quietly. I even wondered whether you were a victim of Katrina and were therefore unable to function for that reason. My concern was exacerbated because you did even getting to the point of acknowledging the early private email carrying the detailed report that your Makefile requested be sent to you. When one is trying, against a background of some urgency, to solve bugs, and there is no feed back from the first responder, then those who are resourceful turn to the appropriate mailing lists. In the circumstances, I make no apology for using the resources appropriately, and I am glad to hear, in the end, you do, with some reluctance, read your email. No doubt you saw how Kris Kennaway <kris@obsecurity.org> not only helped solve the first bug but also prior to doing so, had incorrectly assumed, in the absense of a posting of the full report to the mailing list, that I had failed to follow those instructions. After receiving a copy of the report via the mailing list, he was able to identify a solution to the bug, which you will no doubt implement in your next revision. I hope you thank Kris for his gentle thoughtfulness in responding to the problem when you were not available. >All your questions are FAQ. Since when are bugs FAQ'd? If so what FAQ? Since when did you spend time writing an FAQ about two bugs rather than fixing them? >Search for information on the web and then >contact me privately with *one* message before crossposting FreeBSD >specific questions to PHP mailing lists. Your comment is far from clear but I guess here you are referring to the third issue/bug. The third issue (the way Make deals with --disable-all turned out to be far more complicated than my first brief question raised on FreeBSD-questions mail list a number of days ago and cc'd to you. You refer to an FAQ which presumably mentions this issue. What FAQ is that? Why was that FAQ not referred to in the distribution or at the very least some information given about --disable-all included in the distribution (or even a comment in the Makefile). Searching on the internet during the course of overfull working two days did not turn up anything until I found, late yesterday evening froma posting on an obscure forum, that the third bug was, in fact indirectly caused by the --disable-all "feature of the freebsd ports makefile. Overall I take what is, so far, your first and only response, to these two Makefile bugs and one --disable-all as an acknowledgement that you were not able to respond as quickly as you would ordinarily have wished. But as you are a volunteer I did not feel you had any obligation to respond quickly, so there are no hard feelings on my part. If you feel like upset by the amount of traffic that you receive then you might consider dropping some of the mail lits to which you subscribe, and use the time you save to at least acknowledge requested bug reports and other emails sent directly to you. In which case you would have had no reason to have complained about the traffic and I might have had some chance of getting a genuine and thoughtful response from you. I do however take exception to your lack of concern about the implications of bugs in your Makefile and the content of your response which appears intended to draw attention away from the actual problem. Thanks for geting back to me Have a good day david -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. "It has been said that a human being is rather like an iced doughnut with a hole right through the middle. Sometimes, by their behavior, people draw attention away from the good stuff on top and cause others to focus their concentration on the debris at the bottom."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200509110750.15613.vizion>