Towards becoming a pkg-voip developer

[Tzafrir Cohen]

On Thu, Feb 23, 2006 at 10:58:48PM +0100, Kilian Krause wrote:
> Diego,
> 
> > >As for the sed scripts: this seemed to be a better and more maintainable 
> > >way to describe changes than plain dpatches. But then-again, as I
> > >mentioned, those packages need improving. 
> > >  
> > >
> > I find the seds to be more readable then the dpatch. Also when working 
> > on our svn, it's kinda hard to make dpatch, as we maintain only the 
> > Debian directory and not the full source. 
> 
> svn-buildpackage --svn-ignore --svn-export
> 
> From there you can just poke the source until satisfied and merge back
> the new dpatch. Nothing I find too flawed. Actually that's why I just
> like dpatch; it forces you to keep your diff clean. ;)
> 
> > Tzafrir builds a dpatch on a 
> > separate directory and then imports into the svn, while I made a new 
> > repository in which I have the full source of amportal and I used the 
> > Debian directory as an external dir to the real repository. IMHO, the 
> > sed are more readable, and take less "space". Since I am activly 
> > maintainig that package here, it's my call. If I need to share the 
> > package with Debian, I can be flexible ;-)
> 
> If it's maintained and if it's done well, I don't care what the exact
> details are. Yet my experience is, for snapshots sed is more flexible
> and thus more robust, whereas for release dpatch is better because
> you'll notice code changes more actively and you'll be forced to check
> if you're still doing the right thing. 
> 
> Regarding putting it in Debian, I'd remeber there was license issues
> with the Flash code of amportal. 

That is actually part of the copy of op-panel embedded into amportal.
And this should no longer be an issue because:

1. libming is now back in Sid, making that code buildable again (right?)

2. And anyway, this should not be part of the amportal package, and has
been removed from the freepbx package, along with ARI, in favour of
using separate packages. With luck this separation will work.

> What's the status of freepbx, is it
> DFSG-free or can it be made to comply? 

The core: yes. It is in need of a full review. I know of at least one
problematic component.

-- 
Tzafrir Cohen     icq#16849755  +972-50-7952406
tzafrir.cohen at xorcom.com  http://www.xorcom.com