Comments regarding reconserver_0.9.0-1_amd64.changes
Paul Tagliamonte
paultag at debian.org
Mon Sep 2 15:02:53 UTC 2013
On Mon, Sep 02, 2013 at 11:59:02AM +0200, Daniel Pocock wrote:
>
> Just having a look at where they come from, it appears they originate in
> the sipXtapi source tree
>
> reConServer and reSIProcate use sipXtapi as the underlying media
> framework for RTP
>
> In the sipXtapi repository, we have the WAV files at this location:
Ah neat.
Is there any chance we can rebuild these files at build-time, so that we
have the prefered form of modification (.wav) around for people that
need / want to modify the source?
It'd be even better if upstream did this too :)
>
> https://github.com/sipXtapi/sipXtapi-svn-mirror/tree/master/sipXmediaAdapterLib/
>
> Other packages contain WAV data too, it is not generally perceived as a
> high risk for carrying embedded executable code
Aye, this is more of a prefered form of modification thing (to ensure we
have sources :) )
Thanks so much for your prompt attention,
Paul
--
.''`. Paul Tagliamonte <paultag at debian.org>
: :' : Proud Debian Developer
`. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87
`- http://people.debian.org/~paultag
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20130902/9125094c/attachment-0001.sig>
More information about the Pkg-voip-maintainers
mailing list