Asterisk 1.4 + bristuff

[Mark Purcell]

On Sat, 21 Jul 2007, Faidon Liambotis wrote:
> Kilian Krause wrote:
> > Great! That's wonderful! Can we use the split but keep dpatch to stay
> > with just one patch-system for pkg-voip?
> It can be done but I don't think it's a good idea.
> I use dpatch too, but it doesn't scale. Quilt is perfect for this kind 
> of thing and it will really ease our job.

Hi Faidon,

Welcome to pkg-voip!

Thanks for your work on bristuff, we can certainly use it, of course the
question is what is the best way! Glad our conversation at DebConf 
planted a seed :-)

The problem with quilt is that we aren't familiar with it. That doesn't mean 
that we aren't open to change but that you will need to give us some 
handholding while we work out if quilt is a good thing for us.

Could I suggest rather than uploading direct to trunk for now, lets
create an asterisk/branches/bristuff repo and upload with your quilt
implementation of asterisk+bristuff and if we are confortable we upload 
to experimental in the first instance. So we can have a look at how it works..

> Have a look at it. There are some good slides[1] and a paper[2] that 
> explains them.
> If you really really want one patch system for pkg-voip (which is a 
> rather diverse set, with small, medium and large/heavily patched 
> packages) then quilt should be it.

A lot of projects are using quilt so I'm not saying it isn't a good system,
but a lot of projects are also using cdbs, git and bzr, one thing we wan't
to avoid is the learning cost of a new way of working.

> > Fork is not really the way to go as we duplicate more than 80% of the
> > code. Thus all security fixes would be doubled (and eventually
> > forgotten).
> Agreed; it was only suggested as better than nothing.

Agreed as well.  I don't want to fork and if possible I would like to
keep the single asterisk package with bristuff applied.  
asterisk-{classic,bristuff} was a lot of work.

> >> I've contributing from time to time various stuff to the team, but I 
> >> think it's time to get more involved.

Excellent.  kilian has setup your svn commit rights so you should be good
to go!

> Since you're maintaining openh323/pwlib, I can help there too if you 
> want me too, as you've probably seen from my recent bug reports.
> I have packages for Titan ready for a work project -- we needed ENUM 
> support for GNUgk 2.2.6.
> I'm not sure if you (we? :) want a transition to the new versions or a 
> second source package along the lines of other libraries (e.g. libdb).

kilian is our lead for openh323, so I'll let him comment.

Again welcome!

Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20070721/5c589ec7/attachment.pgp