These release notes cover the following areas:
The SUSE Linux Enterprise Software Development Kit (SDK) can be used for SUSE Linux Enterprise Server (SLES) and SUSE Linux Enterprise Desktop (SLED).
Several packages that are either only on SLES or only on SLED, but needed for the SDK, have been added to the SDK for convenience. The presence of those packages on the SDK does not indicate any support or maintenance entitlement. If you only have a support contract for SLED you are not automatically entitled to support for SLES packages on the SDK and vice versa.
You should be able to re-build any package on SLES or SLED with the SDK DVDs. If you are still using the deprecated CDs, please download the DVDs from http://developer .novell.com/wiki/index.php?title=SLES_SDK.
If you are missing packages on the DVD, please file a bug in the Novell Bugzilla system (http://bugzilla.novell.com). You may also find additional unsupported packages on openSUSE (http://www.opensuse.org).
Please note that for various technical reasons not all SDK packages are available on all SLES hardware architectures.
The SDK does not come with a maintenance or support entitlement. From time to time Novell may release package updates and security fixes online.
If you add the SDK during installation, online update sources for the SDK are added when you register your product.
If you have added the SDK later, please run the Novell Customer Center Configuration in YaST2. This will add the SDK update sources to your configuration. You will not have to re-enter your registration data for this.
In the past, building kernel module packages for different RPM-based Enterprise Linux distributions has been a challenge: There has been no way to use a single .spec file to build distro-specific kernel module RPMs.
Now, through the Linux Foundation Driver Backport Workgroup, key RPM-based distribution vendors have collaborated to support a standard .spec file format and RPM macros for building kernel module packages. Packagers will now be able to use a single .spec file to create distro-specific binary kernel module RPMs. An example kernel module package build structure, complete with the new standard .spec file and sampledriver source code, is available on the SUSE Linux Enteprise SDK 11 SP 1 in the package "samplekmp-source".
Example: libpcap0-devel-32bit package was available in SDK 10, but is missing from SDK 11
Novell supports running 32bit applications on 64bit architectures; respective runtime libraries are provided with SLES 11 and fully supported. With SLE 10 we also provided 32bit devel packages on the 64bit SDK. Having 32bit devel packages and 64bit devel packages installed in parallel may lead to side-effects during the build process. Thus with SLE 11 we startet to remove some of (but not yet all) the 32bit devel packages from the 64bit SDK.
With the development tools provided in the SDK 11, customers and partners have two options to build 32bit packages in a 64bit environment (see below). Beyond that, Novell's appliance offerings provide powerful environments for software building, packaging and delivery.
On the top level of the first CD you will find a very detailed ChangeLog file. Please also read the READMEs on the CD.
In case of encountering a bug please report it through your support contact.
Your SUSE Linux Enterprise Team
Wed Feb 25 18:39:56 UTC 2015