On Fri, Feb 28, 2014 at 05:32:06PM +0100, Michal Hrusecky wrote:
Well, we have so many policies about tracking patches... If we allow people to simply change the content of the tarball (without version change) instead of doing real patch, it's pointless to track patches as we have no idea whether the tarball is upstream one or how many bundled patches it contains.
Well, the point I was making is that I can change the content of a patch in any way I like, so is it ok for you if I submit a package as a single big patch file? Anyway, I don't think this is really about people not doing real patches. In all cases I know where tarball changes happened, openSUSE is the upstream and the development happens in a SCM. In that case, the tarball is automatically generated by some CI like Jenkins. So there'll never be patches in this case. Most of those packages don't put the commit ids in the tarball name, this should probably be changed to make things easier to understand. At some point in the future OBS will maybe support this even more, then you won't even have a tarball anymore, just the unpacked trees. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org