Towards becoming a pkg-voip developer

[Diego Iastrubni]

Hi Lee,

See comments inline.

Tzafrir Cohen wrote:

>>Is "work" the wrong word? First off I would very much like to see the 
>>Xorcom amportal packages built with dpatch instead of using sed in a 
>>install script before the files are copied. Perhaps then they could 
>>be uploaded into sid?
>>    
>>
>
>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. 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 ;-)

I have been working on freepbx. The Debian dir has changed a little, and 
I splited the package correctly (amportal used it's own "op-panel" and 
not the official one from Debian, same for ARI). Both ARI and op-panel 
have integration problems, if you want to do it automatically, and thus 
the  debs produced are not really functional.

If you want, I can send you what I have, and we can split our work. This 
package is not trivial, and to package it the correct way, I will need 
more eyes. IMHO, if we start now, we will have a functional debs when 
freepbx is officially released.

I strongly suggest ditching AMP. It's not maintained, and the amount of 
work to port to freepbx is not worth it. (says he who needs to maintain 
amportal anyway.... :)

(please cc me when replying as I am not subscribed to this list)