status of misdn again

[Tzafrir Cohen]

Hi

I won't comment on most stuff as I'm not familiar enough with the status
of misdn. I'll leave it for others to answer. Just two specific points:

On Sun, Jan 07, 2007 at 11:58:59PM +0100, Simon Richter wrote:
> Hello,
> 
> Tzafrir Cohen wrote:
> 
> >This is not yet a proper package. E.g: it does not include misdn-init
> >and such. I have no idea if it actually close to be working. I see it
> >more of a proof of concept that misdn can be built as a modules package.
> 
> It can be, all the time. I've specifically asked for it to be thrown out 
> of etch because it is unlikely that there is going to be a version that 
> can be sanely packaged.

Fair enough.

> 
> The word "sanely" is the crucial point here. We have module packages 
> that compile on the autobuilders and a -source package that works with 
> both make-kpkg and m-a (at least to my knowledge)

However updating it and building it seem like a pain. Why bother
patching the kernel if you have an external module anyway? If someone
ever wants to adapt it to his personal kernel, he may have a rough time.

> , and there is 
> userspace. But this is where it stops. Our userspace is incompatible to 
> upstream (upstream is broken here, however my fixes were reverted 
> because, well, shared libraries are better than PIC static libraries, 
> and we need PIC on amd64 only, no?). Also, upstream currently has two 
> init systems, one of them being the misdn-init script, the other being 
> an XML-based script. At the same time, the kernel modules still do not 
> perform the slightest bit of sanity checking, and you can easily crash 
> your kernel by loading the modules in the wrong order.
> 
> In short, not for general use. The mISDN support for asterisk cannot be 
> installed currently because it has a file conflict with the asterisk 
> daemon package(s), for which a bug has been filed, however I didn't want 
> to go along just changing it.
> 
> BTW, what was the specific reason for repackaging it?

Making chan_misdn in Asterisk work, mainly. There is now (recent 1.2 and
1.4) chan_misdn in Asterisk. I'm not sure how good it is, but people are
reported to have used it and survived the exeprince.

I packaged a new package mainly as a proof of concept that a simple
external module package can work. That is not a usable package, indeed.
It does not even have misdn-init or any alternative properly packaged.

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir