Adding basic RPM spec file

[BrianSipos]

Closes #286

This also enables and configures ctest for any other use of test running.

[laurencelundblade]

Hi Brian,

Appreciate the addition here. Want to check in on a few of the requirements to maintain this going forward since I'm not familiar with it.

It looks like I should update the spec file every time I make a new release. Mostly the version number and the change log, right?

What is '%setup -q -n QCBOR-1.5' ? I'm asking because it seems to involve versioning. Should it be 1.5.0?

Want to make sure I do this right going forward.

Thx!

[BrianSipos]

Yes, the version number at the top is necessary to update. Though there could be some automation applied to making the update (or produce a spec file from e.g. CMake, but that adds complexity).
The changelog is helpful to include and mandatory for an eventual inclusion Fedora.

There is detailed description of the %setup macro in upstream RPM documentation but because the current spec file obtains its "Source0" directly from Github tarball, which is auto-generated from a release tag, the setup macro must be informed of the directory naming convention that Github uses. Because the Fedora guidelines for naming prefer lower-case the package name qcbor is different than the Github repo/directory name QCBOR.

In the future if release tags follow the same form as the full three-part version name this could be simplified to %setup -q -n QCBOR-%{version} but for now I wanted to get a package that built the actual v1.5 release tarball.

[laurencelundblade]

Understood. Thx for the explanation. I will merge this, but expect you actually want a QCBOR release with this. I will do that soon. It will be 1.5.1, so it will be %setup -q -n QCBOR-1.5.1 since Git puts the ending ".1" in the name of the tar ball.

[BrianSipos]

Yes exactly, the setup name just needs to match the GitHub generated tar directory name.

While it will be nice to see the spec file in a release version, the tools like Copr already allow out-of-source specs. I added a test package at https://copr.fedorainfracloud.org/coprs/bsipos/BSL/package/qcbor/ to verify everything is lined up in the current spec.