Asterisk 1.4 + bristuff

[Kilian Krause]

Faidon,

On Sun, Jul 22, 2007 at 02:45:45PM +0300, Faidon Liambotis wrote:
> 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.

Agreed.


> > -(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?

One source and as many packages as we need to cover the range.


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

More than one asterisk will just reduce the amount of fixes commited and
the work performed on each even more.  Thus we need to make sure that
we've only one asterisk source. Even if it's a bit more tricky to
maintain.

-- 
Best regards,
Kilian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20070722/01f336aa/attachment.pgp