> Most ISVs IMHO need to protect themselves somewhat on Linux > because it is > a platform that can have any level of changes applied at the end-user > level. Meaning, we know what Solaris level or NT level works > through QA > processes, but what if somebody calls me and says I am > running SuSE SLES > with 2.4.18, but I find they have patched the kernel with pre-emptive > stuff, or any number of things that seemed interesting in the dev > community, or say new glibc, and now Sendmail filters or > something are not > working correctly. So you see we have to pick certain levels of the > platform and QA that and call it "known to work". You find an > issue, we > can reproduct that internally on the same platform, much more > reasonable > to keep quality control.
Does the introduction of the LSB and the informal certification scripts for LSB 1.x compliance address this at all? I'm thinking that if the application is written to be LSB x.y compliant, then it should work and be supportable on other LSB x.y compliant platforms, right? -- db
