[Pkg-ime-devel] libchewing1 and scim-chewing

Osamu Aoki osamu@debian.org
Wed, 26 Jan 2005 18:32:41 +0100


On Wed, Jan 26, 2005 at 05:13:39PM +0800, Andrew Lee wrote:
> On Wed, 26 Jan 2005, Osamu Aoki wrote:
> 
> > On Sat, Jan 15, 2005 at 04:43:00AM +0800, Kanru Chen wrote:
> > > He think this is not bad because there are some projects provide it too.
> > > But I also think that providing debian/ in tarball is not good.
> > > I will ask him to split out debian/ from upstream source later.
> >
> > What is happening on this.
> >
> > If it is still there, we can live with it and still can package them.
> 
> After discussed with the author jserv, the reason to have a debian/ is
> only he just wants the debian/ folder right there for testing before he
> make a new release, he can simple use dpkg-buildpackage command to compile
> a new package and overwrite the old one on system.
> 
> I've explain the reason why keep the debian/ folder in release tarball
> isn't a good idea, so he understood and will remove debian/ in next
> release tarball but keep it in his SVN cause he needed.

Oh sure.  He should keep debian/ in his SVN.  But we prefere him
releasing tar bell with "tar --exclude=debian cvzf ....".

> So here we have two way:
> 1) Remove debian/ in currect tarball and rebuild .orig.tar.gz
> 2) Package it as native package and then change it when upstream
>    next release

I go with a minor modification to 2.  We use upstream tar as is while
making needed changes (so we will have small diff.gz.)

> I don't know which one is the proper may? And which one you prefer?

I think it is time to have binary package :-)