MJ Ray <[EMAIL PROTECTED]> writes:
>[EMAIL PROTECTED] writes:
>> [...] It appears that Mike doesn't care too much for Red
>> Hat. Fine, don't support it. But with that attitude, you're ending up
>> not supporting the most used linux distribution out there, and costing a
>> great application a lot of visibility. I have recommended plucker in
>> the past to neophytes, but most of them gave up because installing it
>> was too complicated for them. The last thing they need is to install a
>> new python, when the old one already works for everything but plucker.
>
>Guess what? From the look of Mike's posts, it's probably safe to
>assume that he doesn't use or particularly know Red Hat, but is trying
>the frustrating thing of debugging a problem on a more obscure (to him)
>distribution from reports submitted.
AFAIK, Mike has offerred several things to try, but has not tried doing
any firsthand debugging. I certainly don't fault him for that--- I
don't think anyone should attempt debugging unless they've got something
they can witness the problem on.
>If you have a real live Red Hat distribution and know as much about it
>as you imply, why don't you lend a hand at squashing this bug,
>regardless of whether it's in the Red Hat distribution or the plucker
>code?
I don't mean to imply that I know a lot about Red Hat. I don't,
partiuclarly. It's just the distribution I use. Unfortunately, I don't
know python. If I did, perhaps I could've submitted a patch by now. My
help so far has been with bug reports and responding to more detailed
questions about the behavior.
>PS - I'm interested to know where you get "most used" from.
Primarily, I get it from IDC, PC Data, Netcraft, Corel, Red Hat,
anecdotes, and personal observation.
----Jon
