What to use in packaging

[Isaac Clerencia]

On Thursday 19 January 2006 09:17, Miriam Ruiz wrote:
> Hi,
>
> After reading
> http://kitenet.net/~joey/blog/entry/dpatch_dbs_etc_etc_etc_etc_considered_h
>armful-2005-10-13-06-35.html and listening to all you have said in the list,
> I think the best is not to use any patching system (svn will keep track of
> the changes for us). It also seems that people seems to prefer to
> debhelper, although there is no unanimity in this. Shall we go for
> debhelper then?
Do we really need to agree in this? I mean, I guess small groups of people 
will maintain each package so as long as they agree everything it's ok.

Personally, I use CDBS + simple-patchsys to maintain wesnoth and bygfoot and 
it works great. If we don't have upstream code in the SVN (and I guess we 
shouldn't), a patch system is required and quilt rules :) 

> About svn, it would be nice if someone who had experience packaging with it
> told us what exactly do we need to upload there (the whole upstream code?),
> how to upload (directory structure and so) and how to build from the
> sources there. I guess I'm not the only one who is a bit lost in this. I
> have used svn a lot for development of software, but never for packaging,
> so I'm a bit lost here. Is there any URL to know about it? if not, it would
> be nice to have a few lines in the wiki about that.
In the other three SVN repos that I've seen we just keep the debian dirs in 
SVN, and use the alioth web space to store the upstream tarballs.

You can have a look at the layout we use in the Qt/KDE team:
http://svn.debian.org/wsvn/pkg-kde

Best regards