[Pkg-voip-commits] r1911 - in zaptel/trunk: . debian vzaphfc

[Kilian Krause]

Tzafrir,

> Bristuff comes as a tarball. It has three patches (zaptel, libpri and
> asterisk), a number of subdirectories: zaphfc, qozap, cwain, ztgsm,
> libgsmst, isdnguard. The first four are zapbri kernel modules.
>
> If we follow the same logic, we should add those subdirectories, and
> reduce zaptel's bristuff.dpatch to the original proprotions of
> zaptel.patch.

Right, entirely agreed. Sounds like that'd make life much easier, thus
let's go for it. ;)


> > [snip - 2.4 builds and 2.6.8]
> I believe you lost me here:
> 
> My main point is that mixing Kbuild config and standard makefile is
> yuck. I then suggested some two ways to separate the two. The "proper"
> one (using a file named "Kbuild" will not work on Sarge. I suggested a
> workaround that will.
> 
> On 2.6 there will not be a need to call make directly from that dir:
> you'll only need to add it to the list of targets (as you do for xpp).

Actually I wasn't mixing makefiles. I have a separate copy of makefiles
in debian/makefiles which end up *only* in zaptel-modules. That way the
result is pure 2.6-compatible for sufficiently recent versions. As I
said, if you see that our own pkg-voip sarge backport should also allow
2.4-compatibility, then feel free to move/rename the debian/makefiles in
a way that this works again. Whatever gets me the modules compiled is ok
for me. =)


> > [fixed and modified tor2]
> Just what I thought and why I have not commited that patch. Should
> testers arise, give me a beep.

Sure, will do.

-- 
Best regards,
 Kilian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20060618/454a6a78/attachment.pgp