最佳实践:自己的软件包的版本号

Question

最近，我开始用fpm打包软件。公共制作文件可以在比特桶上找到。

但我对版本号有问题。当我为一个包(例如，fish-shell )生成一个包时，我必须清楚地表明，这个包的原始版本并没有改变，但是这将是我生成的第二个包，这样它就可以替换以前生成的包了。

是否有最佳做法或惯例？

Answer 1

该领域是：

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 turned into a
          Debian  package,  and so there is only one "debianisation" of it
          and therefore no revision indication is required.

          It is conventional to restart the debian_revision  at  ’1’  each
          time time the upstream_version is increased.

          Dpkg  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 compares
          earlier  than  the  presence  of  one   (but   note   that   the
          debian_revision  is  the  least  significant part of the version
          number).

参考文献