On Thu, 2007-10-04 at 10:27 +0200, Stanislav Brabec wrote:
Standard version control system does not work well for packages - spec files changes are concentrated in preamble and %prep and you get a lot of rejects there.
Any version control system would be better than what we have now :) Right now, there is no one-liner (i.e. easy) way to answer any of these questions: * What changed in this package since two weeks ago? * What was the state of this package when $internal_release was done? * Who changed this patch between revisions 6 and 7 of this package? During development, it is very valuable to be able to answer those questions *really quickly* without hunting down old versions by hand, extracting srpms, diffing things, etc. Also, any revision control system keeps a better history than we do in the %changelog part of a specfile. Tools like Stacked Git (stgit) would be very helpful to let us do development while keeping a stack of patches on top of a pristine tarball. They solve the problem of "there are 42 patches in this package, and I need to do a change in patch number 13 and then rebase all the other patches on top of it". Federico -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org