echonesis opened a new pull request, #9379: URL: https://github.com/apache/ozone/pull/9379
## What changes were proposed in this pull request? This PR is a trial effort to **build a single RPM file that incorporates more parameters for enhanced usability and future extensions**. A standard RPM file follows the naming convention: ``` <package_name>-<version>-<release_number>.<distro>.<arch>.rpm ``` Key changes introduced: - `distro (distribution)` and `arch (architecture)` will now be auto-detected for RPM-based systems. - Given the single provider for RPM-based systems, the `java` existence check will only be performed for specific OS versions. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-13439 Related PR: - https://github.com/apache/ozone/pull/8924 ## How was this patch tested? ### Package Build The package was tested locally using the following terminal command to generate RPMs with varying parameters: ``` mvn clean package -Pdeb -DskipTests=true -Drpm.release=<number> [-Drpm.needArch=<bool>] ``` |Parameter |Value |Arch | |---|---|---| |rpm.needArch |true |(auto-detect) | |rpm.needArch |false | noarch | The generated RPM is located under the path: `hadoop-ozone/dist/target/rpm/ozone/RPMS/<arch>` Filename format: `ozone-<version>-<release_number>.<distro>.<arch>.rpm` #### Package Example |System |distro |arch | |---|---|---| |RHEL9 on t2.xlarge |el9 |x86_64 | ### Usage Verification (Example) > Note: We must ensure the packaged architecture is consistent with the architecture of the installation environment. The following steps demonstrate the installation and verification inside a Rocky Linux 9.3 Docker container: ``` (host) > docker run -it --rm --platform linux/amd64 rockylinux:9.3 bash (guest) root> dnf install <ozone.rpm> (guest) root> export JAVA_HOME=<java_home_path> (guest) root> /opt/ozone/bin/ozone version ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
