On Sun, Aug 26, 2007 at 04:55:31PM +0530, Rahul Sundaram wrote:
Charles Curley wrote:
>
>No, Rahul, I will not follow a bug report, for two reasons.
>
>* If the maintainer is not already aware of the problem from reading
> this thread, then he doesn't give enough of a damn for me to spend
> any more time on it.
You aren't expecting every maintainer to subscribe to user lists and
follow all the threads here. Do you? Very very few people have the time
to do this and mailing lists are not a good place to keep track of bugs
which is why bugzilla exists.
Yes, as a matter of fact, I do expect them to subscribe to this
list. Not because they are maintainers per se, but because presumably
they are users as well. It would be a bit difficult to maintain a
package without using Fedora. Of course I could be wrong, which would
explain the state of the Mantis package.
As for following every single thread, that's a straw man argument. It
isn't hard to write a filter to make emails with certain key words
(e.g. "mantis") jump out at you.
>
>* The package is so pathetically broken (see earlier in this thread)
> that the lack of the php-mysql package is irrelevant, another reason
> to believe that the maintainer doesn't give a damn.
Not everyone hits the same problems. I wouldn't assume anything without
even sending any feedback.
The fact that I haven't seen any message to the effect of "Yeah, I saw
that, try this" and only one general "try this list of things to look
at" suggests that nobody has the RPM working.
Has anyone got the Mantis RPM working? Or have folks done what I did:
give up on it and use the upstream tarball?
And another thought, Rahul: maintainers can ignore bugzilla entries
same as they can emails. I've had one bug (189120) oustanding since
2006-04-17, and no-one has yet taken ownership, never mind actually
done anything about it.
--
Charles Curley /"\ ASCII Ribbon Campaign
Looking for fine software \ / Respect for open standards
and/or writing? X No HTML/RTF in email
http://www.charlescurley.com / \ No M$ Word docs in email
Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB