Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #211410

Re: Where'd lsb-compat go?

Show all headers | View raw

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

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-11 20:50 +0200
  Re: Where'd lsb-compat go? Dominic Knight <dominicknight@gmx.com> - 2019-07-12 05:10 +0200
    Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-12 16:50 +0200
  Re: Where'd lsb-compat go? Tixy <tixy@yxit.co.uk> - 2019-07-12 10:10 +0200
  Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 16:20 +0200
    Re: Where'd lsb-compat go? Michael Stone <mstone@debian.org> - 2019-07-15 16:30 +0200
      Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 21:40 +0200
        Re: Where'd lsb-compat go? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-15 21:40 +0200
        Re: Where'd lsb-compat go? Stefan Monnier <monnier@iro.umontreal.ca> - 2019-07-15 21:50 +0200
          Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 22:10 +0200
            Re: Where'd lsb-compat go? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-15 22:20 +0200
              Re: Where'd lsb-compat go? Nicolas George <george@nsup.org> - 2019-07-15 23:00 +0200
                Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 23:20 +0200
              Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 23:00 +0200
              Re: Where'd lsb-compat go? Gene Heskett <gheskett@shentel.net> - 2019-07-15 23:20 +0200
            Re: Where'd lsb-compat go? Gene Heskett <gheskett@shentel.net> - 2019-07-15 23:00 +0200
          Re: Where'd lsb-compat go? Andy Smith <andy@strugglers.net> - 2019-07-16 14:30 +0200
    Re: Where'd lsb-compat go? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-16 08:50 +0200
      Re: Where'd lsb-compat go? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-16 14:50 +0200

csiph-web