LSB 4.0 Beta 1

Printer-friendly versionAt long last, I am pleased to announce the availability of LSB 4.0 Beta 1. To help with coordinating the beta process, we have published a Web page with all information on accessing LSB 4.0 Beta 1. That page can be found at: https://www.linuxfoundation.org/en/LSB_4.0_Beta You can view and download the specification from there, or download our test suites, Software Development Kit, and Sample Implementation. The improvements in LSB 4.0 can be found in our preliminary release notes: https://www.linuxfoundation.org/en/ReleaseNotes40 Some of the highlights: - The SDK now supports LSB 3.0, 3.1, 3.2, and 4.0 in one single download, and can switch between them at application build time. - The Sample Implementation is brand-new, and is now based on the Conary technology from rPath. - A new set of tools for the Sample Implementation makes use of the SI much easier. - The SDK now provides a tool for easy building of LSB-compliant packages. - Many updates to already-shipping standards, such as glibc, Qt 4, and GTK+. - Many new standards, such as Cairo, NSS, and the Java language. Please note that there are a number of issues still to resolve with LSB 4.0, and that new issues may come up. Please visit our bug tracker at: http://bugs.linuxbase.org/ to see the current status of LSB 4.0, and to report any issues you may discover. Some important known issues: - All new standards, as well as trial-use standards in LSB 3.2, are subject to approval by the LSB workgroup. That vote has not happened, and thus any of the new standards in LSB 4.0 may be made trial-use or dropped, depending on the results of the vote. - Due to a problem with some of the build servers, the s390 tests and tools are not available yet. We hope to make them available very shortly; please check the beta status page for their status. - The new Sample Implementation takes a long time to build, and thus we are only releasing the x86 version immediately. As the other architectures are built, their SI will be added to the beta status page. - We will be reorganizing our infrastructure for signing packages and repositories before the final release of LSB 4.0, but that is not ready yet. We are not aware of any breaches of security, but are improving our infrastructure to prevent such a breach in the future. - The best-effort option in the SDK is intended to be LSB-compliant, but some of the spec work is not yet finished. It is possible that we may not be able to support best-effort in the standard at this time.