English Chinese (Simplified)
Perform a test build using `tito build --test`
Tag the release with `tito tag` (add `--use-version` if necessary)
Push the tag to your git repo using `git push --follow-tags`
and Copr will take care of the rest.
Packaging from source tarballs
You can use a similar process to manage someone elses software on Copr, i.e. build from a tarball downloaded from upstream.
To do so, the following changes need to be made to the procedure described above:
Instead of the unpacked sources, download & commit the source tarball you want to package to your repository
Instead of modifying the source directly, add any changes you need to make in the form of patch files. List these as `PatchX:` in the spec file
Also in the spec file, set the `Version:` back to whatever version the program is at and `Source0:` back to the tarball URL. You can use macros like `%\{version}` for the latter to automatically follow version changes.
Modify tito's `.tito/tito.props` to, one, not try to build a source tarball and two, bump the `Release:` instead of the `Version:` when tagging
```
builder = tito.builder.NoTgzBuilder tagger = tito.tagger.ReleaseTagger ```
Don't do any tito templating
The rest of the procedure stays the same. If you make changes to the package without changing the source, you can just tag a new release with tito. If you do update the source tarball, you need to update the `Version:` field and reset `Release:` to `0%\{?dist}` before tagging.
The tarball-adapted version of the project can be found in the `https://pagure.io/copr-tito-quickdoc/tree/foreign-sources[foreign-sources]` branch of the git repo.