No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
<!-- page was renamed from Extras/UsefulScripts | <!-- page was renamed from Extras/UsefulScripts | ||
--> | --> | ||
= | = Tools for package automation = | ||
fedpkg interacts with only one package, whereas the reality is many maintainers work with multiple RPMs, often with inter-build dependencies, from potentially multiple source code locations. | fedpkg interacts with only one package, whereas the reality is many maintainers work with multiple RPMs, often with inter-build dependencies, from potentially multiple source code locations. | ||
This page is attempting to gather together lists of scripts and tools which edit spec files programmatically and are layered on top of fedpkg/koji. | This page is attempting to gather together lists of scripts and tools which edit spec files programmatically and are either layered on top of fedpkg/koji/copr, or act as a more agile bypass. | ||
Hopefully, you will find one of these tools useful. However, the author of this page has as a real motivation arguing that the underlying infrastructure should support some of this directly. | Hopefully, you will find one of these tools useful. However, the author of this page has as a real motivation arguing that the underlying infrastructure should support some of this directly. | ||
Line 26: | Line 26: | ||
Interacts with upstream git + Bugzilla, generates spec file data. | Interacts with upstream git + Bugzilla, generates spec file data. | ||
=== mclazy === | === mclazy === |
Revision as of 13:26, 12 March 2015
Tools for package automation
fedpkg interacts with only one package, whereas the reality is many maintainers work with multiple RPMs, often with inter-build dependencies, from potentially multiple source code locations.
This page is attempting to gather together lists of scripts and tools which edit spec files programmatically and are either layered on top of fedpkg/koji/copr, or act as a more agile bypass.
Hopefully, you will find one of these tools useful. However, the author of this page has as a real motivation arguing that the underlying infrastructure should support some of this directly.
tito
Probably the most advanced layered tool; spec file changelog generation, interaction with koji.
rdopkg
https://github.com/redhat-openstack/rdopkg
Used by Red Hat/OpenStack: https://openstack.redhat.com/Main_Page
anaconda/scripts/makebumpver
https://github.com/rhinstaller/anaconda/blob/master/scripts/makebumpver
Interacts with upstream git + Bugzilla, generates spec file data.
mclazy
https://github.com/hughsie/mclazy
Pulls tarballs, edits spec files, interacts with chain-build.
rebase-helper
https://github.com/phracek/rebase-helper
the-new-hotness
https://github.com/fedora-infra/the-new-hotness