On Sat, Nov 12, 2016 at 10:51:32PM +0100, Andrey Gursky wrote: > > For the record, pjproject is currently used by a single other package: > > asterisk. Upstream of asterisk recommends applying a set of their own > > patches: > > > > http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=tree;f=third-party/pjproject/patches;hb=13 > > Tzafrir, thanks for pointing this out. I've just noticed that these > patches have been included in pjproject. > > Bernhard, what do you think about including the bug-fix patches from > the Ring's pjproject also? For the same reasons as for Asterisk [1]:
No objections per se, as long as the changes do not interfere with Asterisk. Ideally they have already been accepted upstream and are only small, verifiable changesets. Looking at the list Alexandre at least some of them don't really fall into this category. Especially, although I'm disgruntled by the OpenSSL mess, switching to GnuTLS that close to the freeze is something I want to avoid. Also adding symbols that might cause a transition to be necessary in case we would have to revert them. If you have a cleaned up list of patches you definitely need, ideally with upstream commits and/or explainations why they won't affect Asterisk's use of pjproject, please file a bug on pjproject and we'll have a look. Bernhard
signature.asc
Description: Digital signature