[Pkg-gauche-devel] Maintaining patches with quilt?

NIIBE Yutaka gniibe at fsij.org
Fri Feb 26 13:35:12 UTC 2010


Jens Thiele wrote:
> Or do you suggest to drop git-buildpackage altogether? I prefer using a
> vcs/scm to manage patches instead of doing it manually.

I don't think it's worth to have *another* diversion of Gauche
repository.

If we really needed to use SCM for Debian packaging, I would recommend
you guys to join Gauche project at sf.net to use Svn, and make a
branch for Debian packaging (possibly use svn-buildpackage).  I don't
say Git is bad idea and Svn is better.  No, my point is that
maintaining Debian package should be easier.

Well, let me explain my idea straight.  My point is that:

 (1) NMU should be easier
     Specifically, I wish a Debian developer could just do like:
       $ apt-get source gauche
       [Change as she needs]
       [Build]
       [Upload to ftp-master]

 (2) Updating from new upstream should be easier
     Specifically, I wish we could just do like:
       $ cd gauche-old-version
       $ uscan
       $ uupdate ../gauche-new-version.orig.tar.gz
       $ cd ../gauche-new-version
       [Change as she needs]
       [Build]
       [Upload to ftp-master]

 (3) Contributing back to upstream should be easier

So far (I mean, 0.8.13), we don't meet those conditions unfortunately.

> But in the end for me everything is fine as long as gauche 0.9.x
> will get into squeeze ;-)

I see.  Let me try my own challenge in next week.  My plan is like this:

  Step 1: Move to 3.0 (quilt) format.
  Step 2: Update to 0.9.
  Step 3: Introduce libgauche0 package

Because introducing libgauche0 will result new gauche package to be
into NEW queue, we need some extra care for this step.  I would like
to have our changes to Debian archive as soon as possible.
-- 



More information about the Pkg-gauche-devel mailing list