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

[YAEGASHI Takeshi]

Niibe-san,

Welcome to the list!  I'm glad to see you here.

2010/2/26 NIIBE Yutaka <gniibe at fsij.org>:
> 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.
>> 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:

Ok.  Actually I'm not inclined to manually maintain patchset files
considering yet another troublesome aspect of it, but I wouldn't care
much about packaging ways either.  Now look forward to seeing the
result.


>  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.

Well, we need to reconsider that packaging strategy (having
gauche/libgauche0)... it would be better to remain current way after
all.

Almost all dependent packages need the interpreter executable (gosh),
so it would not make much sense to have gauche binaries separated in
such a manner.  Indeed, naming libgauche0 is encouraged by Debian
Policy Manual 8.1, but most maintainers seem to give priority to
simplicity and understandability over lintian warnings.

http://lintian.debian.org/tags/package-name-doesnt-match-sonames.html

And having gauche-gdbm for libgdbm bindings seems meaningful to me.
The upstream author has decided to provide a -gdbm package separately
in other distro (see Gauche.spec).  It's not so good idea to confuse
users by inventing another way.

Regards,
-- 
YAEGASHI Takeshi <yaegashi at debian.org>