On Tuesday 28 December 2010 12:07:54 Sven Burmeister wrote:
So since there are no drawbacks of having a version number in the package's name but only advantages, IMHO it should be part of the package-name.
I believe that we all agree that we should have a proper version number in the package. So that we can ask an user to do `rpm -q $package` and get a correct version number. However this brings two questions up, namely: 1) If we have a proper version number in the package, does this mean that we also have to give the tarball itself a version number ? Or would it be sufficient to have %{packagename}-git.tar.bz2 or %{packagename}-svn.tar.bz2 ? 2) What kind of version do we give packages coming from a git repository ? This is especially important as that KDE itself is also slowly moving to git instead of SVN. So a commit number is being replaced by a git-string. We could of course use the shortened git-string, however is this really according to the RPM standards? The rpm standards describes that a higher version will replace a package with a lower version. But is the git string always higher than the previous one ? Currently a lot of packages makes use of a date behind the word git (version becomes x.y-gitYYYYMMDD), but how do we indicate if we have multiple updates on that same day ? The last question I also already raised to Will and Dirk, but it would be worth to see what the community thinks about this. Just my 15 cents :-) Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org