Curently, there's a dependency on fedora RPMs for building che-code.

if [[ $(uname -m) == "x86_64" ]]; then LIBKEYBOARD="\
      https://rpmfind.net/linux/centos/8-stream/AppStream/x86_64/os/Packages/libxkbfile-1.1.0-1.el8.x86_64.rpm \
      https://rpmfind.net/linux/centos/8-stream/PowerTools/x86_64/os/Packages/libxkbfile-devel-1.1.0-1.el8.x86_64.rpm"; \
    elif [[ $(uname -m) == "aarch64" ]]; then LIBKEYBOARD="\
      https://rpmfind.net/linux/centos/8-stream/AppStream/aarch64/os/Packages/libxkbfile-1.1.0-1.el8.aarch64.rpm \
      https://rpmfind.net/linux/centos/8-stream/PowerTools/aarch64/os/Packages/libxkbfile-devel-1.1.0-1.el8.aarch64.rpm"; \
    else \
      LIBKEYBOARD=""; echo "Warning: arch $(uname -m) not supported"; \
    fi

This approach isn't ideal from a product security perspective for a number of reasons:

• hardcoded version can't be updated via Freshmaker respins; requires manual monitoring & updates
• RPMs are not available from RHEL 8 content sets, only CentOS
• PowerTools repo is not a standard content set available OOTB in RHEL8 (so might not be available in Brew)
• only x64 and aarch are supported; we need Z and Power too

So, while it's POSSIBLE that doing an rpm install, collecting the binary files from the container, and using that tarball to shoehorn files into Brew might work ... it's reallllllly not ideal and goes in the reverse direction to CRW-3080.

An alternative approach could be to remove dependency on libkxb, as we did for ds-theia:

https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-8/devspaces-theia/Dockerfile#L46-L51