On 7/15/19 9:25 AM, Michael Stone wrote:
On Mon, Jul 15, 2019 at 09:15:19AM -0500, Kent West wrote:
However, that didn't solve the issue; apparently the SMA release on
the "Description:" line of output from "lsb_release -a" instead of
the "Release:" line.
And now we see one of the big reasons why the LSB initiative failed:
the vendors didn't write to the spec, they just wrote to what worked
on their preferred distro. Which is basically what they did without
LSB--making the effort of implementing LSB a complete waste of time.
I'm glad you posted this, for three reasons:
1) it allowed me to realize I wrote "the SMA release" instead of "the
SMA relies". I hate when I produce unintelligible output.
2) It answers my question of why Debian seems to have deprecated LSB. I
don't know anything about programming to the LSB spec, but your comment
makes it clear that Quest (<-- a little negative publicity there) failed
to support the LSB properly, and vendors like that have made, as you
say, "the effort of implementing LSB a complete waste of time."
3) It spurs me to ask: So, if not via LSB, what is the canonical way to
programatically determine the version of an installed Debian setup?
Thanks!
--
Kent
