extracting patches from the ancestry graph (was: recreating historic packages)

martin f krafft madduck at debian.org
Wed Oct 1 09:38:26 UTC 2008

also sprach Teemu Ikonen <tpikonen at gmail.com> [2008.09.30.2329 +0200]:
> At the moment, yes, but the new dpkg with version 3.0 quilt format
> builds the source package from sources with the patches applied.
> This enables one to store the integrated sources in VCS, generate
> debian/patches from branches (e.g. with topgit) and build
> a debian.tar.gz with simply calling dpkg-source, providing that an
> orig.tar.gz is also available.

Assuming we have a number of feature branches, we may well have to
resolve conflicts among them, so an integration branch seems like
the right way forward. So unless we just build the package from the
integration branch to produce a monolithic patch, your algorithm is
something to focus on! I am still not convinced that it is possible
to extract historic patches from the ancestry of a tag on the
integration branch, but I'd love to be proven wrong! Unfortunately,
I won't be able to look into this again before next week.

 .''`.   martin f. krafft <madduck at debian.org>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems
"durch frauen werden die höhepunkte des lebens bereichert
 und die tiefpunkte vermehrt."
                                                 - friedrich nietzsche
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
Url : http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/attachments/20081001/a0c31521/attachment.pgp 

More information about the vcs-pkg-discuss mailing list