At present the asterisk and libpri ports include a customised version of a very large patchset called "bristuff". This patchset is Asterisk version specific and therefore causes significant delays in updating the FreeBSD port of the fast-moving Asterisk project. The bristuff patches are only of significant use to a subsection of Asterisk users (mainly European users where ISDN-2/ Basic-Rate ISDN is more common, and then only to those who actually want to use it with BRI). Fix: I suggest a repo-copy of net/asterisk to net/asterisk-bristuff and of misc/libpri to misc/libpri-bristuff (this would mirror the approach taken by at least one Linux distribution, Debian). The "old" net/asterisk and misc/libpri ports could then have the bristuff patches removed and be updated in a timely fashion to follow the asterisk release sequence, whilst the -bristuff versions would continue to be maintained as now. I would be willing to take over as maintainer of the non-bristuff ports if the existing maintainer (sobomax) were not willing to maintain the parallel versions. How-To-Repeat: Asterisk is at the time of filing this PR at 1.2.7.1 The FreeBSD port is at 1.2.4
Responsible Changed From-To: freebsd-ports-bugs->portmgr Please do repo-copy.
Responsible Changed From-To: portmgr->fjoe Sorry, I decided to create slave ports instead to keep in sync with main asterisk port.
There was no portrevision bump on the libpri change which has broken portupgrades of asterisk... This is biting people already. http://lists.digium.com/pipermail/asterisk-bsd/2006-April/001721.html Any chance of a quick resolution on this (pretty please :-> ) -- Thomas Sandford
hi! On Thu, Apr 27, 2006 at 01:45:19PM +0100, Thomas Sandford wrote: > There was no portrevision bump on the libpri change which has broken > portupgrades of asterisk... > > This is biting people already. > > http://lists.digium.com/pipermail/asterisk-bsd/2006-April/001721.html > > Any chance of a quick resolution on this (pretty please :-> ) Fixed. /fjoe
Responsible Changed From-To: fjoe->portmgr Please repocopy ports/net/asterisk -> ports/net/asterisk-bristuff ports/misc/libpri -> ports/misc/libpri-bristuff
I have no problems with moving bri-extended version into a separate port. I would like to continue maintaining the original one, though. -Maxim
State Changed From-To: open->repocopy Please repocopy ports/net/asterisk -> ports/net/asterisk-bristuff ports/misc/libpri -> ports/misc/libpri-bristuff
State Changed From-To: repocopy->open Repocopies completed.
Responsible Changed From-To: portmgr->fjoe Repocopies completed.
State Changed From-To: open->closed Repo-copied libpri-bristuff and asterisk-bristuff updated and connected to the build.