SUSE Linux Enterprise Software Development Kit 12 SP2

Release Notes

These release notes are generic for all products based on SUSE Linux Enterprise
Software Development Kit 12 SP2.

Product to be released: November 2016

Publication Date: 2016-10-19, Version: 12.2.20161007

1 SUSE Linux Enterprise Software Development Kit
2 SDK Features
3 Packages and Functionality Changes
4 Providing Feedback to Our Products
5 Legal Notices

1 SUSE Linux Enterprise Software Development Kit

The SUSE Linux Enterprise Software Development Kit (SDK) can be used for SUSE
Linux Enterprise Server and SUSE Linux Enterprise Desktop.

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.

As the SDK is targeting SLES and SLED, it may contain packages which are only
useful and can only be installed in combination with one of SLES and SLED, not
with both. This is a feature not a bug.

You should be able to re-build any package on SLES or SLED with the SDK media.

If you are missing packages on the media, file a bug in the SUSE Bugzilla
system (http://bugzilla.suse.com). You may also find additional unsupported
packages on openSUSE (http://www.opensuse.org).

Note

Note

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, SUSE may release package updates and security fixes online.

If you add the SDK during installation, online update repositories for the SDK
are added when you register your product.

If you have added the SDK later, run the SUSE Customer Center Configuration in
YaST. This will add the SDK update sources to your configuration. You will not
have to re-enter your registration data for this.

2 SDK Features

2.1 New Packages for Protocol Buffers Available

libprotobuf9 protobuf-devel has been added to the SDK to allow you to develop
applications with the Protocol buffers language.

Protocol buffers are a language-neutral, platform-neutral, extensible mechanism
for serializing structured data - similar to XML, but smaller, faster, and
simpler. You define how you want your data to be structured once, then you can
use special generated source code to easily write and read your structured data
to and from a variety of data streams and using a variety of languages. For
more information, see https://developers.google.com/protocol-buffers/ (https://
developers.google.com/protocol-buffers/).

2.2 GNOME Builder IDE Has Been Added

The SLE SDK now ships with GNOME Builder which is a new Integrated Development
Environment specifically for GNOME application developers.

2.3 Byebug Has Been Added

Byebug is a simple-to-use, feature-rich Ruby 2 debugger that is also used to
debug YaST. It uses the TracePoint API and the Debug Inspector API. For speed,
it is implemented as a C extension.

It allows you to see what is going on inside a Ruby program while it executes
and offers traditional debugging features such as stepping, breaking,
evaluating, and tracking.

3 Packages and Functionality Changes

3.1 New Packages

3.1.1 libxapian22 and libxapian-devel Have Been Added

The SLE 12 SP2 SDK now ships with Xapian. Xapian is an open-source search
engine library, released under the GPL v2+. It is written in C++ and has
bindings to allow use from Perl, Python, PHP, Java, Tcl, C#, Ruby, Lua, Erlang
and Node.js.

3.2 Deprecated Functionality

3.2.1 librpcsecgss3 Has Been Removed

librpcsecgss (packages: librpcsecgss3, librpcsecgss-devel) has been removed.
With the release of libtirpc, the development of libsecgss stopped and it fell
out of use. We recommend using libtirpc instead.

3.2.2 Packages for YaST Developer Documentation Have Been Dropped

All packages containing developer documentation relating to YaST were dropped
from the distribution. This affects all packages following the naming scheme 
yast2-*-devel-doc.

The yast2-*-devel-doc packages are not needed any more. With YaST now being
written in Ruby and hosted on GitHub, documentation can now be generated
online. It can be accessed at http://www.rubydoc.info/find/github?q=yast (http:
//www.rubydoc.info/find/github?q=yast).

4 Providing Feedback to Our Products

On the top level of the first product medium you will find a detailed ChangeLog
file. For more information, also see the READMEs there.

In case of encountering a bug, please report it through your support contact.

Your SUSE Linux Enterprise Team

5 Legal Notices

SUSE makes no representations or warranties with respect to the contents or use
of this documentation, and specifically disclaims any express or implied
warranties of merchantability or fitness for any particular purpose. Further,
SUSE reserves the right to revise this publication and to make changes to its
content, at any time, without the obligation to notify any person or entity of
such revisions or changes.

Further, SUSE makes no representations or warranties with respect to any
software, and specifically disclaims any express or implied warranties of
merchantability or fitness for any particular purpose. Further, SUSE reserves
the right to make changes to any and all parts of SUSE software, at any time,
without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be
subject to U.S. export controls and the trade laws of other countries. You
agree to comply with all export control regulations and to obtain any required
licenses or classifications to export, re-export, or import deliverables. You
agree not to export or re-export to entities on the current U.S. export
exclusion lists or to any embargoed or terrorist countries as specified in U.S.
export laws. You agree to not use deliverables for prohibited nuclear, missile,
or chemical/biological weaponry end uses. Please refer to http://www.suse.com/
company/exports/ for more information on exporting SUSE software. SUSE assumes
no responsibility for your failure to obtain any necessary export approvals.

Copyright (C) 2010- 2016 SUSE LLC. This release notes document is licensed under
a Creative Commons Attribution-NoDerivs 3.0 United States License (CC-BY-ND-3.0
US, http://creativecommons.org/licenses/by-nd/3.0/us/.

SUSE has intellectual property rights relating to technology embodied in the
product that is described in this document. In particular, and without
limitation, these intellectual property rights may include one or more of the
U.S. patents listed at http://www.suse.com/company/legal/ and one or more
additional patents or pending patent applications in the U.S. and other
countries.

For SUSE trademarks, see SUSE Trademark and Service Mark list (http://
www.suse.com/company/legal/). All third-party trademarks are the property of
their respective owners.

(C) 2016 SUSE

