-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 07 March 2003 02:56, Maks Orlovich wrote: > What you're also forgetting is that Mandrake is not the only group that's > affected. Changes Mandrake makes to KDE, Gnome, Mozilla, etc., reflect on > people's opinion of the respective software; and cause maintenance hassles. > I already had to close 2 reports of galaxy-kde's broken masking (including > spending time explaining to the user why this was happening; quite a bit of > time, I must add, time which could be better spend trying to fix actual > bugs in KDE); and that bug is only scratching the surface, there are > multiple major problems there.
Yes, that's true. But is more a problem for Mandrake as a vendor, then e.g. for KDE. If something doesn't work on Mandrake's KDE but works elsewhere (even because the packager made a hack to get it to work), it will make Mandrake look bad, not KDE, at least not that much. People go and complain to their vendor, they didn't buy KDE, they bought/downloaded Mandrake Linux. But otherwise I agree, Mandrake is not the only party affected here. > That's known regression on the 3.1.x branch (marked release critical show > stopper for KDE3.1.1); IMHO a sane solution is to back out the patch -- the > problem it was trying to solve is pretty minor anyway (what is it with > merging 99% of branch patches, anyway? ;-) ) Finaly somebody told me what's going on here. There is yet another bug about this in Bugzilla - 2861. Could you have a look at that, please ? Maybe it is the same issue and should be closed/resolved the same way. Jan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+aJCun11XseNj94gRAhU3AKDnRu8y1sCDxbUb98rLlE7YgFVImwCeODwK lqW7nx0YO/2Odfe8UXj83ho= =u16B -----END PGP SIGNATURE-----
