The wikis are now using the new authentication system.
If you did not migrate your account yet, visit https://idp-portal-info.suse.com/

Portal:Leap/openSUSE:Step

Jump to: navigation, search
Steplogo.png

What is openSUSE Step?

openSUSE Step is a community effort to rebuild SUSE Linux Enterprise (SLE) from the released SLE sources packages. This is done openly in the openSUSE instance of the Open Build Service (OBS) with the intention to stay fully binary compatible and to be as closely source-compatible as possible with SLE.

Why openSUSE Step?

openSUSE Leap 15.3 inherits its base operating system from SLE 15 SP3. On aarch64, powerpc64, and x86_64, openSUSE directly uses binary packages from the enterprise side. Additionaly to these architectures, openSUSE also supports architectures that SLE does not provide, such as armv7hl, which is relatively popular with openSUSE users, according to results from a recent openSUSE Arm Community Survey. For those, we now build fully compatible binary packages from the published SLE sources in the OBS.

openSUSE Step is not intended to be an end user distribution. It does not replace, or provide an alternative to openSUSE Leap. Step is an intermediate building block ("step") to enable derived community distributions like openSUSE Leap or other future community derivatives.

What is currently in openSUSE Step?

There are currently four versions defined and existing in parallel: openSUSE Step 15, 15-SP1, 15-SP2, and 15-SP3. These are hosted under the openSUSE project namespace in OBS and uses the published sources from SLE plus minimal modifications needed for being able to build them from sources while incorporating the published maintenance updates.

openSUSE Step currently covers i586/x86_64, and armv7hl. More architectures, such as RISC-V, can be added based on contributor interest and resource capacities.

How is this related to openSUSE Leap?

With the "Closing the Leap Gap" project moving forward, openSUSE Leap will become a layered cake of binary packages from three different origins:

  • The base os binary packages directly copied from SLE,
  • A small set of currently around 50 packages that provide an openSUSE branding overlay to these SLE packages
  • openSUSE Backports overlay, which provides a wealth of applications and libraries that everyone likes to use on top.


Leap with openSUSE Step architecture comparison.png


openSUSE Step provides an alternative for Leap architectures that have no SLE equivalent like 32-bit architectures. The other two groups of originated packages will be the same like for the other architectures.

In addition to that, openSUSE Step provides everyone access to build logs and the ability to have "a build validated" project repository of SLE for community customization, which serves as a collaboration space for related projects that would like to derive from SLE package sources.

Leap transitioned to a new way of building Leap releases in the fall of 2020 through a prototype project called Jump. The Jump prototype was used as a proof of concept, but no longer exists; it did prove to work at building a distribution and bringing the code streams of both openSUSE Leap and SLE closer together. The proof of concept was implemented for building the release of Leap 15.3.

How is this related to openSUSE Tumbleweed ?

It is not related. openSUSE Tumbleweed is a rolling release distribution entirely managed and built by the openSUSE community with a strong focus on continuously integrating new upstream releases while preserving a high-quality rolling update without major regressions. Tumbleweed is an origin for the next major SLE release. There is no direct general relationship between Tumbleweed and maintained SLE releases. The openSUSE Backports project is often sourcing changes from Tumbleweed.

Does openSUSE Step allow community contributions?

Yes, community contributions are welcome if they improve buildability from sources and do not modify binary compatibility in any way. The mission of openSUSE Step is being fully compatible and for all practical purposes an equivalent drop in for SLE.

For (internal) quality validation purposes, Step x86_64 architecture will also be built alongside other architectures but it will not be delivered into openSUSE Leap or otherwise be available for now.


How can I contact the openSUSE Step team?

The openSUSE Step team is hanging out on Freenode in the #opensuse-step channel. Issues can be reported in GitHub under https://github.com/openSUSE/step/issues .