On Tue, Aug 11, 2009 at 11:17 PM, Jamie Zawinski wrote: > That's nonsense. Either the hack in a particular release of xscreensaver > works properly, or it doesn't.
I am not talking about xscreensaver releases, but distribution releases. They include the Xorg stack with various GL bugs. Let me give you an example: flurry used to make machines freeze, due to bugs in Xorg. It was not possible to solve the Xorg bugs in time for the distribution release, so we disabled flurry. Now it does not crash any longer, so we can ship flurry again. > And it's not like these things actually change with any great frequency. > You're solving problems that don't actually exist. I wish you were right :) In the end the user see some screensaver crash their machine, and he/she is not interested in what the real problem or the real fix (TM) is, or developers arguing about who to blame. > Moving hacks around at all is silly and confusing. Just get it right the > first time. Anything else is a cop-out and waste of effort. Which hacks to be shipped by default and which to offer optionally will change over time, also because new fancy hacks are added and some will look old and uncool. It is also about automating things so we avoid mistakes when doing things manually. Example: When we shipped flurry again, we forgot to add back the man page. And when a new hack will be included upstream, it is now a one-liner to get it correctly included. This is enough reason for us to apply this patch. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
