[Pkg-silc-devel] Using dpatch or not?

[Jérémy Bobbio]

Hi!

I would like to get opinions on using dpatch (or similar tools) in the
Debian SILC packages...

By using svn-buildpackage, we already have a system that can easily
track differences between upstream source and the debian one for a given
package.

Without any other tools, it's already pretty easy to add or rollback
changes to upstream source in a clean way.  We can keep the debian
.diff.gz to its minimum which can ease proofreading of the package.

Using dpatch or quilt has some advantages though: every patch is
logically separated and can be sent upstream in a feature oriented way.
Upstream can easily decide to integrate the patches and we just have to
remove a file to acknoledge that (instead of solving merge conflicts).

I would personally prefer to stay with keeping our modifications in the
subversion repository only.  I really prefer to be able to proofread any
changes between to package versions using debdiff than to analyse diff
of diff.  But I won't mind to use dpatch or quilt if there's a strong
preference on using such tool.

Cheers,
-- 
Jérémy Bobbio                        .''`. 
lunar at debian.org                    : :Ⓐ  :  # apt-get install anarchism
                                    `. `'` 
                                      `-   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-silc-devel/attachments/20070526/3c140bb6/attachment.pgp