[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: StarlingX looking at alternatives to CentOS

Paul, thanks for this, more below about build tools

On 1/15/21 7:25 PM, Paul Wise wrote:
On Fri, Jan 15, 2021 at 6:30 PM Saul Wold wrote:

I am a member of the StarlingX Community [0], which is a cloud
infrastructure stack that presents Kubernetes, containerized OpenStack
along with a grouping (flock) of management tools.

Please note that Debian bullseye has packages for Kubernetes and
OpenStack, I expect those teams would welcome help maintaining them.

StarlingX uses a custom kernel and patches some userspace with a custom
build system based around mock and rpmbuild.

Please consider getting your Linux kernel patches included upstream,
there are a lot of advantages to that.


Some of the other aspects of your custom kernel might be useful to
apply to the Debian Linux kernel build.

Please send your userspace patches upstream too.

I'd encourage you to switch to a non-custom build system too, I expect
one of the many existing ones would suit your needs.

We would like to contribute to the Debian eco-system as well of course.

There are lots of ways to help Debian, please especially note the ways
organisations can help Debian at the end of this page:


The how-can-i-help tool can point out more specific ways to help:


Our concerns have to do with
1) Build Tooling
We have been looking at pbuilder and debbuild, ,but want to understand
if there are automated building scripts (I did find buildd).

Debian uses wanna-build for management of builds and sbuild for running
individual builds.


There are many other options for this and the derivatives census lists
info about what each derivative uses.


I have been actively looking at these pages, but have not set anything up around creating a wanna-build or sbuild (yet).

It's not clear to me how these tools handle dependencies between packages when building packages from source, such as building a library package that an userspace package might depend on.

I come from the OpenEmbedded/Yocto Project space where we have bitbake that parses the recipe files and then computes dependencies between tasks and packages automagically.


3) Status of Bullseye
Again I have seen the release pages.

The best way to find out the status of bullseye for your use cases is
to install, run and test it. Of course it will be fluctuating until the
final freeze before the release.

5) lots of other considerations around patching userspace, adding
missing packages to the debian ecosystem, creating custom repos (either
with DAK or repropro).

There are many different tools for apt repos and the derivatives census
lists info about what each derivative uses, reprepro is popular.


6) other unknowns of transitioning from CentOS -> Debian

Please take a look at the Debian derivatives guidelines:


Debian jargon may differ to CentOS, check out our glossary:



Reply to: