asterisk dapper.2114_to_dapper.2234 diff

Jonas Smedegaard dr at jones.dk
Sun Aug 6 21:56:39 UTC 2006


On Sun, 6 Aug 2006 22:20:01 +0100 Mark Purcell wrote:

> On Sunday 06 August 2006 19:04, Jonas Smedegaard wrote:
> > I have experienced some trouble and broken behaviour with installing
> > and upgrading the current asterisk packages in sarge, etch and
> > unstable, but have found the packaging somewhat a mess so have not
> > yet filed bugreports about it. 
> 
> I think one of the issues is we are trying to maintain both
> asterisk-classic and asterisk-bristuff from the same source tree.
> 
> As a result debian/rules has become quite complex, which two runs
> through the build process one for each package.  This means that
> maintenance is becoming a little complex, which means that mistakes
> are slipping through.

That is also my impression of the cause of the problem.


> Perhaps, we would be better off running the two packages from
> different upstream source trees, ie have one asterisk.xxx.orig.tar.gz
> and a different  asterisk+bristuff.xxx.orig.tar.gz.  Then the two
> aren't totally coupled and can progress at their own pace.
> 
> I don't personnaly have any bristuff hardware, so it is difficult to
> debug, but others are interested in its maintenance.

I believe it possible to keep them together, and simplify by using cdbs.


> > I'd like to help cleaning up the packaging 
> > and switching to using cdbs, if it is of any interest - so this
> > thread (when cleared up the Debian<->Ubuntu prioritation) is highly
> > interesting for me.
> 
> I'm very keen on cdbs, but others in pkg-voip mileage varies.  The
> problem with the complex packaging we have for asterisk is that cdbs
> will struggle to keep up, with the current dual build enviroment.   A
> two seperate single build packages would be suited to cdbs.

The main obstacle is probably cdbs lack of handling multiple different
compilations of same source. I believe I have solved that! I was only
really active directly in the cdbs development before it turned into
team-maintainance, and when I recently joined the team the others did
not understand the need for my proposed enhancements, so they were
rolled back again :-(

I'll have a look at it!


Why is asterisk_fix not just included in postinst?


 - Jonas

-- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20060806/2320147f/attachment.pgp


More information about the Pkg-voip-maintainers mailing list