On Jan 13, 2004, at 5:39 PM, Keith Conger wrote:
Hi,
This is unstable.
You are right, it is unstable tree. But you miss my point. People on the list (Martin in this case) just tell users to remove things first, and i see no evidence that anyone even considered this to be a problem. It *IS* a problem, a MAJOR problem, and it needs to be taken seriously.
Martin: You are wrong. It is frankly NOT my responsibility to figure out why the problem occurred. As a user of the package, is only my responsibility to report failure, that is it. For your convenience, I even used FinkCommander, which included relevant system details. Manually removing is a workaround, not a fix. I am not 'forgetting the time factor'. My main point here is that this was a bug in the package, and you acted like it was not (in multiple emails.) I figured out why it failed on my own because apparently, noone else cared. Why should I have to? Where is the bug tracker item on this?
Yes, if something is a bug, make sure you point that out. You can include the workaround. If you really think these issues don't cause people to leave fink, you haven't been around long enough or talked to enough users. We see them on IRC all the time (usually in #opendarwin, after having rm -rf /sw)
And dude Martin, get this in your skull - fink-gnome-core is **NOT** A FORUM. I DO NOT HAVE TO READ IT. fink-gnome-core is a 'group maintainer' which was made world-readable so people wouldn't be blocked out of helping to maintain it. I STRONGLY object to creation of new fink forums i have to search every time i need to report a problem. I absolutely refuse to do so. I thought this group maintainer stuff was a bad idea in the first place, this is yet another reason why. Now WE ALL get to maintain it! Wohoo! Thats the same as no maintainer at all, if i have to read fink-gnome-core! Anything you 'announce' on fink-gnome-core is being 'announced' only to fellow maintainers of the fink-gnome packages. Since it is not a forum, the maintainers of fink-gnome-core are responsible for replying to each email personally. Should i now read Ben Reed's email before reporting KDE bugs? no.
And this is NOT truly a 'recent thing with big updates', there are packages which have been in unstable for weeks which do not upgrade. This is not specific to gnome. I believe the system-xfree86 upgrade from 10.2 is still broken, in fact it is in the FAQ. Noone cares. Half our perl modules don't upgrade.
-Ben
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
