Added Debian bits, man page #14
Conversation
| @@ -1,3 +1,10 @@ | |||
| nccl (1.1.0) trusty; urgency=medium | |||
There was a problem hiding this comment.
The convention is to add a -1 to the end of the version string, like 1.1.0-1. But it's optional.
debian_revision
This part of the version number specifies the version of the Debian package based on the upstream version. It may contain only alphanumerics and the characters + . ~ (plus, full stop, tilde) and is compared in the same way as the upstream_version is.
It is optional; if it isn't present then the upstream_version may not contain a hyphen. This format represents the case where a piece of software was written specifically to be a Debian package, where the Debian package source must always be identical to the pristine source and therefore no revision indication is required.
It is conventional to restart the debian_revision at 1 each time the upstream_version is increased.
The package management system will break the version number apart at the last hyphen in the string (if there is one) to determine the upstream_version and debian_revision. The absence of a debian_revision is equivalent to a debian_revision of 0.
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
|
Can we not check the .deb packages into git directly, but instead attach them to the tagged release? See .deb packages here for an example: |
|
Created release |
Yeah just like that, but in this fork obviously. Packaging scripts look good to me, however I haven't actually tested them. |
|
Will submit a superceding request |
Version bumped. Checked in new .deb packages binaries.