Request: Pre‑built XStudio RPMs for EL 9 **and** EL 10 (EPEL)

Summary

Provide official RPM packages of XStudio for Enterprise Linux 9 (RHEL 9, AlmaLinux 9, Rocky 9) and Enterprise Linux 10 (RHEL 10, AlmaLinux 10, Rocky 10) and publish them in the corresponding EPEL repositories.

Why this matters

• XStudio is a professional, open‑source video‑editing suite used by creators, educators, and small production houses.
• EL 9 already ships many multimedia tools (FFmpeg, GIMP, etc.) via EPEL 9, but XStudio is missing, forcing users to build from source or use unofficial repos.
• Adding XStudio to both EPEL 9 and EPEL 10 brings feature parity across the current RHEL family, simplifying deployment and automated updates for all supported EL releases.

Current situation

Users must compile from source or rely on community‑maintained builds, which lack the security‑update workflow that EPEL provides.

Requested versions

• Any recent stable release (e.g., XStudio 2024.2 or newer).
• Packages should be named xstudio.x86_64 (and xstudio-debuginfo, xstudio-libs if applicable).

Build dependencies (already available in EPEL 9 & EPEL 10)

• qt5-qtbase, qt5-qtsvg, qt5-qtdeclarative (or Qt 6 equivalents for EL 10 if preferred)
• ffmpeg, libavcodec, libavformat, libavutil, libswscale
• libx264, libx265, libvpx
• zlib, glib2, openssl, pcre2
• Development tools: gcc, make, cmake, pkg-config, rpm-build

All of these libraries are present in the current EPEL 9 and EPEL 10 repos, so a rebuild should be straightforward.

Additional notes

The upstream project already supplies an RPM spec file; no need to start from scratch.
If any patches are required for EL 10 (e.g., path changes for newer qt6 libraries), I’m happy to contribute them.
Linking to the existing Bugzilla tickets (for EL 9 and EL 10) can help coordinate effort:
    EL 9 request – [Bug #XXXXX] (replace with actual ID)
    EL 10 request – [Bug #YYYYY] (replace with actual ID)

Thank you for considering this addition to the official XStudio packaging. It would greatly benefit the entire RHEL ecosystem!

Start by locating the upstream RPM spec file and reviewing the listed build dependencies and existing EL packaging requirements. Validate whether the project builds for EL 9 and EL 10, then check the EPEL submission process; done means installable xstudio packages are available in both corresponding EPEL repositories.