| Message ID | 156459232623.7075.3064492825922924284.stgit@Palanthas (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | automation: build Xen in openSUSE Tumbleweed | expand |
On 7/31/19 11:58 AM, Dario Faggioli wrote: > openSUSE comes in two flavours: Leap, which is non-rolling, and released > annualy, and Tumbleweed, which is rolling. > > Reasons why it makes sense to have both (despite both being openSUSE, > package lists in dockerfiles being quite similar, etc) are: > - Leap share a lot with SUSE Linux Enterprise. So, regressions on Leap, > not only means regressions for all openSUSE Leap users, but also helps > prevent/catch regressions on SLE; > - Tumbleweed often has the most bleeding-edge software, so it will help > us prevent/catch regressions with newly released versions of > libraries, compilers, etc (e.g., at the time of writing this commit, > some build issues, with GCC9, where discovered while trying to build > in a Tumbleweed image). > > Note that, considering the rolling nature of Tumbleweed, the container > would need to be rebuilt (e.g., periodically), even if the docker file > does not change. > > Signed-off-by: Dario Faggioli <dfaggioli@suse.com> Acked-by: Doug Goldstein <cardoe@cardoe.com>
diff --git a/automation/build/suse/opensuse-tumbleweed.dockerfile b/automation/build/suse/opensuse-tumbleweed.dockerfile new file mode 100644 index 0000000000..2676a87c85 --- /dev/null +++ b/automation/build/suse/opensuse-tumbleweed.dockerfile @@ -0,0 +1,68 @@ +FROM opensuse/tumbleweed +LABEL maintainer.name="The Xen Project" \ + maintainer.email="xen-devel@lists.xenproject.org" + +ENV USER root + +RUN mkdir /build +WORKDIR /build + +RUN zypper ref && zypper up -y --no-recommends +RUN zypper install -y --no-recommends \ + acpica \ + bc \ + bin86 \ + bison \ + bzip2 \ + checkpolicy \ + clang \ + cmake \ + dev86 \ + discount \ + flex \ + gcc \ + gcc-c++ \ + gettext-tools \ + git \ + glib2-devel \ + glibc-devel \ + glibc-devel-32bit \ + gzip \ + hostname \ + libSDL2-devel \ + libaio-devel \ + libbz2-devel \ + libext2fs-devel \ + libgnutls-devel \ + libjpeg62-devel \ + libnl3-devel \ + libnuma-devel \ + libpixman-1-0-devel \ + libpng16-devel \ + libssh2-devel \ + libtasn1-devel \ + libuuid-devel \ + libyajl-devel \ + lzo-devel \ + make \ + nasm \ + ncurses-devel \ + ocaml \ + ocaml-findlib-devel \ + ocaml-ocamlbuild \ + ocaml-ocamldoc \ + pandoc \ + patch \ + pkg-config \ + python \ + python-devel \ + systemd-devel \ + tar \ + transfig \ + valgrind-devel \ + wget \ + which \ + xz-devel \ + zlib-devel \ + && \ + zypper clean -a
openSUSE comes in two flavours: Leap, which is non-rolling, and released annualy, and Tumbleweed, which is rolling. Reasons why it makes sense to have both (despite both being openSUSE, package lists in dockerfiles being quite similar, etc) are: - Leap share a lot with SUSE Linux Enterprise. So, regressions on Leap, not only means regressions for all openSUSE Leap users, but also helps prevent/catch regressions on SLE; - Tumbleweed often has the most bleeding-edge software, so it will help us prevent/catch regressions with newly released versions of libraries, compilers, etc (e.g., at the time of writing this commit, some build issues, with GCC9, where discovered while trying to build in a Tumbleweed image). Note that, considering the rolling nature of Tumbleweed, the container would need to be rebuilt (e.g., periodically), even if the docker file does not change. Signed-off-by: Dario Faggioli <dfaggioli@suse.com> --- Cc: Doug Goldstein <cardoe@cardoe.com> Cc: Wei Liu <wl@xen.org> --- .../build/suse/opensuse-tumbleweed.dockerfile | 68 ++++++++++++++++++++ 1 file changed, 68 insertions(+) create mode 100644 automation/build/suse/opensuse-tumbleweed.dockerfile