RPM Packaging

Question

RPM Packaging

rphillips opened this issue 2 years ago · comments

What happened?

I received some tips for packaging conmon-rs RPMs from @cgwalters. Generally bootupd looks like a good example. The bootupd github releases contain a source tar and a vendor tar. The bootupd.spec uses both tarballs to generate the resulting rpm.

Starting points could be:

On conmon-rs tag, create a release with a vendor tarball and a source tarball using a GH action

What did you expect to happen?

None

How can we reproduce it (as minimally and precisely as possible)?

None

Anything else we need to know?

No response

conmon-rs version

NONE

$ conmonrs --version
# paste output here

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

Additional environment details (AWS, VirtualBox, physical, etc.)

Sascha Grunert · Answer 1 · Tue Aug 02 2022 14:53:26 GMT+0800 (China Standard Time)

Sounds good, would it make sense for us to generate the RPM for every commit?

Ryan Phillips · Answer 2 · Tue Aug 02 2022 23:56:06 GMT+0800 (China Standard Time)

The RPM generation can be done on https://src.fedoraproject.org/ or other build servers... I don't think we actually have to build the RPMs in this repo.

Ryan Phillips · Answer 3 · Thu Aug 04 2022 23:22:57 GMT+0800 (China Standard Time)

Tagged releases now upload the vendor and source payloads.

Ryan Phillips · Answer 4 · Fri Aug 05 2022 03:49:10 GMT+0800 (China Standard Time)

@lsm5 also added a copr build #602

I added a spec on pagure here https://pagure.io/conmon-rs to use the Releases.