Naming issue for meego 1.0 related packages

[Chen Lei]

2010/7/11 pbrobinson at gmail.com <pbrobinson at gmail.com>:
>
> I don't agree with the easier, and the releases are all built on tags.
>
> Well someone will have to get the policy added to the packaging
> guidelines. There's guidelines for using VC repos but not for using
> tar files from other distros source packages.
>
> Peter

It seems no guideline forbid us to use tarballs extracted from
upstream repo.  I think using git repo for meego packages have more
harm than benefit, because the most important feature for rpm is
people can validate the md5sum of the source tarball easily. Unless
special case we can't find a way to get reliable souce tarballs, I
think it's better to use tarballs rather than get source files from
VCS. Meego repo is reliable place to get source tarballs, they also
have bugzilla against those modules and they are the upstream. Also,
it seems some meego packages don't have a public VCS(e.g. fennec-qt)
or public VCS is not active currently(e.g. scim-panel-vkb-gtk[1]).
Meego 1.0 use scim-panel-vkb-gtk 0.1.7, meego 1.1 use 0.1.8. but the
latest version in the git repo is 0.1.6.

[1]https://bugzilla.redhat.com/show_bug.cgi?id=615047

Regards,
Chen Lei