RE: [lsb-futures] Re: [Lsb-desktop] Re: KDE representation
"Banginwar, Rajesh" <[email protected]> Tue, 16 Aug 2005 15:49:17 -0700
| Newsgroups | gmane.linux.lsb.discuss |
|---|---|
| Message-ID | <B5677069E3D9994D9EE1C7295072EA9608090C73@orsmsx402.amr.corp.intel.com> |
May be I am missing something here, the app will work on any LSB certified distro since library B and C will provide the ABI required for the App. The ABI coming from lib D will be taken care of by the application developer himself by distributing the library.=20 The application will have to do this only for the libraries not covered by LSB, of course. > -----Original Message----- > From: Stuart Anderson [mailto:[email protected]] > Sent: Tuesday, August 16, 2005 3:26 PM > To: Banginwar, Rajesh > Cc: [email protected]; [email protected]; lsb- > [email protected] > Subject: RE: [lsb-futures] Re: [Lsb-desktop] Re: KDE representation >=20 > On Tue, 16 Aug 2005, Banginwar, Rajesh wrote: >=20 > > LSB also requires that these distributed library need to be LSB > > compliant. Why not loosen that restriction? So with this, LSB will allow > > the application developers to allow distribute any non-LSB library and > > not require them to be LSB conformant. App A depends on libraries B,C > > and D. B and C are covered in LSB and hence not a problem for App A; but > > library D is not covered, but shipped with App A making sure the library > > is available and installed at /opt hierarchy. >=20 >=20 > If you loosen the restriction, then you've just moved the portability > problem from the App to lib D. The same problems still exist. This > doesn't > allow any guarantees to be made that app will run on any LSB certified > distro. >=20 > Stuart >=20 > Stuart R. Anderson [email protected] > Network & Software Engineering http://www.netsweng.com/ > 1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F > BD03 0A62 E534 37A7 9149