Křištof Želechovski (giecrilj@stegny.2a.pl) wrote:
Dnia wtorek, 10 września 2013 18:05:42 Adam Spiers pisze:
Jan Engelhardt (jengelh@inai.de) wrote:
Just call the f'ng Version: 1.5+git and spell out everything else in the %description. The Release: will automatically increase everytime you commit and ensure that people get the latest version your hands produced, even if there was branch-hopping or shipping an older git snapshot (a revert in essence).
Hiding important metadata in %description is going to cause problems. For example, a decent bugreport will contain version numbers of all relevant rpms involved in the bug, but it will not contain a copy'n'paste of running rpm -qi on all those rpms. So your proposed change would require a lot of developers to have to say "thanks but please can you run rpm -qai and send me the output" every time they receive a bug report. Not a good idea.
The bug report will contain version numbers and release numbers. Developers can recover the exact source from the release number, can't they?
Nope, the release number is controlled entirely by OBS. If someone updates the git tarball without modifying the version number, the only way to find out would be to connect to the host in question (assuming that's possible) and run rpm -qi on the relevant packages. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org