Richard Biener (rguenther@suse.de) wrote:
Or completely alternative to this whole scheme just package a diff alongside a released tarball.
Nice thinking outside the box :-)
Bonus: you get the possibility of being able to verify its contents with an available signature.
I don't understand this point. You mean verify the contents of the released tarball? But if the diff is not also verified then isn't that rather pointless? Also, a git hash is equivalent to an integrity check (albeit an unsigned one).
Bonus 2: less load on the source server(?)
tar_scm caches, so I'm not sure that argument's too compelling.
Bonus 3: easier to see what the changes since a release are.
Easier for who? Only for packagers, and excluding the one who packaged the diff (since they already had to have a clone of the repo in order to make the diff in the first place). So again, not hugely compelling IMHO.
Oh, and then provide incremental diffs whenever you update the package rather than exchanging the diff.
In the absence of a source service to do this (which I suspect would be quite hard to write), I think it will create a lot more work for the packager :-/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org