Proposal: Automate rpm build and publication

[abn]

Proposed automation for rpm package builds. Pending changes:

1. Add .copr.enc.
2. Add openssl decrypt command in script.
3. Enable travis builds.

@trollixx I was not sure if you intended the automation for publishing builds at @zealdocs/zeal to be triggered by changes here or for me to keep maintaining at abn/zeal-rpm. If the latter is the case, feel free to reject this one and I'll go ahead and make the required changes to my repository. If not, I'd recommend that you add or send me a .copr.enc file along with the travis openssl command generated, I can fix up the PR to include that before the merge. Once merged the travis build can be enabled.

[alunux]

I really don't know why we need other repository, instead use official repository from Fedora?

[abn]

@alunux the intention here is not to replace the distro provided packages, but instead provide a channel for consuming the latest releases sooner for those that need it. This is one of the capabilities that the Fedora team has enabled with copr.

The latency between upstream package release and disto package update is sometimes significant, and especially for major/minor version updates. Distro packages need to respect their own policies and processes around version upgrades etc. For example, 0.6.0 is not yet available in the official repositories and neither is the zeal packages available in epel-release.

As added benefit, this provides a shorter feedback loop for any rpm packaging issues.

[trollixx]

@abn Can we have two "channels" in COPR? One for tagged version, and another triggered on each commit.

[abn]

@trollixx that can be done yes. I just need to rework the automation a bit to use the short commit-sha in the NVR so we can do that cleanly.

[trollixx]

@abn have you ever gotten to publishing to zealdocs/zeal COPR? Are there any issues with that?