why isn't rpm release tag redundant? -


from rpm .spec file documentation, version tag intended correspond version of software being packaged. release tag intended increment new build of .rpm.

what point of release tag then??

if software has not changed in meantime , version same, definition software , behaves same, , .rpm file before, release should same. suppose original .rpm file lost need recreate it, , there no changes, then, of course recreated file should before - 1 wants in case of no changes software.

i don't need release tag, please explain me.

added: docs @ http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html say

(...)if necessary repackage software @ same version, release should incremented.(...)

maybe not mean? maybe intended here is, "repackage software @ same version, there may minor changes not deserve new version, increment release instead". meant here??

there lot of factors go binary rpm file, beyond upstream version of source code. compiler/configure options, default config files, init scripts, pre/post install actions, , set of files packaged. 1 of these might need changed after initial build. example, heartbleed, 1 might want rebuild openssl heartbeat feature turned off. in case, upstream version hasn't changed , there needs way distinguish 2 builds. release tag enables this.


Comments

Popular posts from this blog

windows - Single EXE to Install Python Standalone Executable for Easy Distribution -

c# - Access objects in UserControl from MainWindow in WPF -

javascript - How to name a jQuery function to make a browser's back button work? -