Question
Does Plone 6 backend with Classic UI requires any (apt) packages to work? other than the pip packages?
Plone 6 backend with Classic UI Installation via pip
A Plone 6 backend with Classic UI Installation via pipseems to need only python3-venv.
Packages installed by plone-backend
The Dockerfile of plone-backend installs the following packages (see Dockerfile#L13):
dpkg-dev, gcc, libbz2-dev, libc6-dev, libffi-dev, libjpeg62-turbo-dev, libldap2-dev, libopenjp2-7-dev, libpcre3-dev, libpq-dev, libsasl2-dev, libssl-dev, libtiff5-dev, libxml2-dev, libxslt1-dev, wget, zlib1g-dev, python3-dev, build-essential
Some of the packages above are installed both in python:3.9-slim-bullseye and in plone-backend:
dpkg-dev, gcc, libbz2-dev, libc6-dev, libffi-dev, libssl-dev, wget, zlib1g-dev,
The following packages are installed only in python:3.9-slim-bullseye:
dirmngr, gnupg, libbluetooth-dev, libexpat1-dev, libgdbm-dev, liblzma-dev, libncursesw5-dev, libreadline-dev, libsqlite3-dev, make, tk-dev, uuid-dev, xz-utils,
And the following packages are installed only in plone-backend:
build-essential, libjpeg62-turbo-dev, libldap2-dev, libopenjp2-7-dev, libpcre3-dev, libpq-dev, libsasl2-dev, libtiff5-dev, libxml2-dev, libxslt1-dev, python3-dev.
The Dockerfile of plone-backend installs also the following packages (see Dockerfile#L45):
git, libjpeg62, libopenjp2-7, libpq5, libtiff5, libxml2, libxslt1.1, lynx, netcat, poppler-utils, rsync, wv, busybox, gosu, libmagic1, make
Which of those packages are actually requirements for Plone 6 and which ones are only needed for Docker, Make or other tools?
Plone 5 requires following packages:
python3.9-dev, python3.9-tk, python3.9-venv, build-essential, libssl-dev, libxml2-dev, libxslt1-dev, libbz2-dev, libjpeg62-dev, libreadline-dev, wv, poppler-utils