Asterisk 1.4 + bristuff

[Faidon Liambotis]

Kilian Krause wrote:
  > Yes, svk may come close. That why I support it if we really have to
> manage that huge amount of patches for now. Yet we should keep in mind
> that we want to push most of the logic upstream and reduce our packaging
> to "just wrapping upstream sources into debs".
For such cases, dpatch is OK.
We can't do that with bristuff however and we need to maintain a big 
patchset indefinitely.

That's exactly why I proposed quilt in the first place.

> -(snip)-
>> Anyway, just give it a try and a thought.
>> Until you decide otherwise, I'll continue working with dpatch, at least 
>> in trunk/.
> 
> Good, please nevertheless make a branches/experimental to get us used to
> it. Make sure you add it to the /snapshots/pkg-voip-config to have the
> checkout take place for Buildserver.NET. I'm really eager to see it
> perform nicely with the next bristuff update.
I'll do that, but have in mind that it needs a bristuffed libpri.

We first have to resolve the libpri issues first.

And of course we have to decide on the most important issue:
are we going for a split classic/bristuff packaging or not?

What's the consensus?

Personally, I'd prefer to have a single "asterisk" package, but I don't 
mind that much.

Regards,
Faidon