Bug 96315

Summary: Asterisk/libpri should have a separate bristuff port/version
Product: Ports & Packages Reporter: Thomas Sandford <freebsduser>
Component: Individual Port(s)Assignee: Max Khon <fjoe>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Thomas Sandford 2006-04-25 14:00:29 UTC 
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
Comment 1 Max Khon freebsd_committer freebsd_triage 2006-04-25 20:37:14 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->portmgr

Please do repo-copy.
Comment 2 Max Khon freebsd_committer freebsd_triage 2006-04-25 20:40:38 UTC 
Responsible Changed
From-To: portmgr->fjoe

Sorry, I decided to create slave ports instead to keep 
in sync with main asterisk port.
Comment 3 thomas 2006-04-27 13:45:19 UTC 
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
Comment 4 fjoe 2006-04-27 14:09:05 UTC 
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
Comment 5 Max Khon freebsd_committer freebsd_triage 2006-05-11 11:06:03 UTC 
Responsible Changed
From-To: fjoe->portmgr

Please repocopy 

ports/net/asterisk -> ports/net/asterisk-bristuff 
ports/misc/libpri -> ports/misc/libpri-bristuff
Comment 6 Maxim Sobolev freebsd_committer freebsd_triage 2006-05-11 21:03:11 UTC 
I have no problems with moving bri-extended version into a separate 
port. I would like to continue maintaining the original one, though.

-Maxim
Comment 7 Max Khon freebsd_committer freebsd_triage 2006-05-21 22:41:10 UTC 
State Changed
From-To: open->repocopy

Please repocopy 

ports/net/asterisk -> ports/net/asterisk-bristuff 
ports/misc/libpri -> ports/misc/libpri-bristuff
Comment 8 Joe Marcus Clarke freebsd_committer freebsd_triage 2006-05-22 04:47:28 UTC 
State Changed
From-To: repocopy->open

Repocopies completed.
Comment 9 Joe Marcus Clarke freebsd_committer freebsd_triage 2006-05-22 04:47:28 UTC 
Responsible Changed
From-To: portmgr->fjoe

Repocopies completed.
Comment 10 Max Khon freebsd_committer freebsd_triage 2006-06-03 16:31:27 UTC 
State Changed
From-To: open->closed

Repo-copied libpri-bristuff and asterisk-bristuff updated 
and connected to the build.