status of misdn again

[Simon Richter]

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.

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), 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?

    Simon