Open KlavsKlavsen opened 7 years ago
How about using FPM for producing the RPMs? We have used that to generate the official Debian packages, see the build target in the Makefile.
@mattock this is more about building Yum repositories containing RPMs, rather than building Freight as an RPM. (I publish RPMs for Freight itself via Fedora's EPEL project.) To build repos, you'd use the Python createrepo tool.
i agree that FPM ought to be able to support Yum and other types of repo, and it the command line does appear to have been designed with that in mind. I'm sure there's a fork containing Yum support somewhere, but I've been unable to find it now (it means digging through the GitHub 'network' I think).
Currently I just extended my freight-add script - so it (when its an rpm) - simply copies the rpm into $reponame/yum/... and runs rpmsign --addsign and create repo on the repo. freight should probably just do the same - and then sign the yum repo as well.
It would be cool if freight add - also handled rpm repo's - and gpg signing of rpms. It would need to "know to fail" - if one tried to add an rpm to a debian repo..
Either you could simply add a setting to a conf file (which is per repo) - simply had VARCACHE and VARLIB setting for rpm.. or if freight was made to prefix with type.. so you could set a config setting: HANDLEYUM=true|false HANDLEAPT=true|false and prefixed repo with $VARCACHE/YUM/$usual path - as it already does with VARLIB dir.
What do you think of the idea? (then one could add other rpm-based systems, which does not support yum repo format as well).
I might hack a little on it if I get time.. if we agree on how it should be implemented (in helicopter view :)