Not entirely we think:
LSB does help in the the layout for scripts, like /usr/local/xxx for
sendmail and /etc/init.d etc, but the two main distros we certify Rh adv
srv and SuSE SLES both seemingly will have differences in the near future
in respects to libs, SLES will be taking an approach with NGPT (Next
Generation Posix Threads) an IBM sponsored project, while RH will be going
with another flavor, each differs, one is M:N while the other is 1:1. The
confusion for us now is do we just compile against whatever is in glibc or
do we go back to a port for ea distro and have some advantages?
I believe we willl maintain a single xxx123-LNX.rpm moving forward, LSB
helped us eliminate xxx123-SuSE.rpm and xxx123-RH.rpm, but it reamins to
be seen I think how close the LSB spec will hold Linux distos for ISVs
like us and how well those distros comply. It is not un-common for Os
vendors to "create" new standards, or claim there are new ones and
everybody should do this or that :~)
Regards,
Jon
Jon R. Doyle
Sendmail Inc.
6425 Christie Ave
Emeryville, Ca. 94608
(o_
(o_ (o_ //\
(/)_ (\)_ V_/_
On Tue, 26 Nov 2002, David Boyes wrote:
> > 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
>
