I almost made a comment, like the one i'm about to make, months ago but I decided to drop it and not create flames. But here's my opinion.
Suse doesn't make tripwire, they don't maintain tripwire, they don't do anything except add tripwire to their distro. They add, best guess, over 3000 different rpm packages to their distro. I don't find it terrible that each and every one of those aren't fully quality tested and that they don't work the first time. Sure, they shouldn't include it if they didn't test it, but really who is going to sit there and test each and every package. Is there anyone here who test each and every package distributed with Suse? I think not.
No, but our users certainly have a good go at it. Scripted regression tests to make sure that at least every executable at least executes are not difficult, and I expect it is what Suse currently do + more, except things sometimes slip through the net. I know make mistakes and so does everyone else. I certainly do not expect manual testing of every package - yuk.
So what, a package doesn't work, go get the source and compile/install it yourself. That's what Linux is all about, you don't have to use the proprietary vendors stuff ALL the time.
True. IMHO if the software you want to use is critical then you should compile it yourself.
It doesn't really bother me that a package doesn't work, if I really want that package then I'll find other means to obtain it.
yup, but there are a lot of users who will want convenience (home users, for example, who do not want to spend lots of time delving into documentation, etc.)