google
RPMbuild Support
The *.spec files already produce these RPM packages:
cuttlefish-base-0.9.29-1.el9.x86_64.rpm
cuttlefish-user-0.9.29-1.el9.x86_64.rpm
cuttlefish-integration-0.9.29-1.el9.x86_64.rpm
cuttlefish-orchestration-0.9.29-1.el9.x86_64.rpm
I'd probably would need more information, eg. what to build with bazel
and also, which packages are even required and which files to package.
It seems to work so far, just needs more testing on the target system.
Had to edit the init-script, because there is no command rh_status.
This is the command, which I use for testing the package-scripts ...
sudo dnf -y remove cuttlefish-* && \
tools/buildutils/build_packages.sh && \
sudo rpm -i ./tools/rpmbuild/RPMS/x86_64/cuttlefish-base-0.9.29-1.el9.x86_64.rpm \
./tools/rpmbuild/RPMS/x86_64/cuttlefish-user-0.9.29-1.el9.x86_64.rpm \
./tools/rpmbuild/RPMS/x86_64/cuttlefish-orchestration-0.9.29-1.el9.x86_64.rpm \
./tools/rpmbuild/RPMS/x86_64/cuttlefish-integration-0.9.29-1.el9.x86_64.rpm
@daedroza That wasn't such a great idea, because it only has caused a mess, when accidentally merging. Might try later on a Linux machine, where I still have a pristine version and can actually test the scripts. This will probably be a new PR, with the commits squashed into one then. The amount of files changed somehow doesn't look good.
Thanks - I've rebased your changes here on my personal fork: https://github.com/daedroza/android-cuttlefish/commits/rpmbuild
But I haven't gotten time to test as I'm waiting for F42 release. Hopefully it works out of the box! With your force push I see more changes, the diff is too big for me to review.
@daedroza I'm going to start over with a new branch and then PR, to get rid of the conflicts. My mistake was, that I didn't sync the remote fork first and then also pressed the wrong button.
https://github.com/google/android-cuttlefish/pull/942