These release notes cover the following areas:
Major features of the SP3 release are:
The OpenFabrics Enterprise Distribution (OFED) packages have been moved from the SDK to SLES between SP2 and SP3. Please remove the according packages if you are upgarding a SLED+SDK to SP3 and running into package dependency issues.
Major features of the SP2 release are:
The SDK provides two new system imaging solutions:
KIWI currently does not use libzypp for creating images, but smart. This can lead to different images as installing with YaST. We will offer later a version of KIWI which supports libzypp instead of smart.
Yup is a new tool to mirror maintenance updates from the Novell Customer Center for SUSE Linux Enterprise 10 products. It is especially targeted for environments which are not directly connected to the NCC via internet. Using yup something like an offline mirror can be provided, see http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=3065146&sliceId=SAL_Public and http://www.novell.com/linux/technical_library/deploying_mirroring.pdf . The yup package also contains a script "yup2zlm", a prototype to inject yup-mirrored patches more easily into an existing ZLM 7.2 server. /usr/share/doc/packages/yup/Advanced_SLES10_Patching_0.2.pdf
The SUSE Linux Enterprise Software Development Kit (SDK) can be used for SUSE Linux Enterprise Server (SLES) and SUSE Linux Enterprise Desktop (SLED).
Some highlights are:
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.
The DVD edition of the SLE SDK comes with Eclipse 3.1.1 on this hardware architecture. The newer Eclipse 3.2.1 is not available yet because it requires Java 1.5 for building. Java 1.5 was not available for SLE 10 on this hardware architecture at the time the SDK was released.
Updating from NLD 9 with the SDK or SLES 9 with the SDK for SLES 9 is not recommended and mostly untested. You should start from a fresh SLES or SLES 10 installation if possible.
If you want to update from SLES 10 GA or SLED 10 GA, we recommend that you add the SLE 10 SDK as an add-on product during update by checking "Include Add-On Products from Separate Media" and selecting the SDK installation sources.
Although most existing PHP 4 code should work without changes, there are some few backward incompatible changes. A list of this changes can be found at: http://www.zend.com/manual/migration5.incompatible.php
The SDK is an add-on product. It can be added during installation, so the additional packages that come with the SDK can be selected and installed right from the beginning, or later.
If you install the SDK on top of a SLES or SLED that has the latest maintenance patches applied, you may get dependency errors in some cases if you don't also use the latest SDK patches.
To avoid this, please make sure that you re-run the Novell Customer Center (NCC) Configuration in YaST2 right after you have added the SDK installation source to your system, but before you install any packages from the SDK. This will add the SDK update channel to your setup.
YaST will then automatically use newer packages from the update channel if available. Your system needs to be connected to the Internet for both running the NCC Configuration and receiving actual maintenance updates.
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
Fri Sep 14 12:13:46 UTC 2018