ports/128140: update devel/pwlib to 2.4.1 to fit GNOME 2.24

Eric L. Chen lihong at ieee.org
Fri Oct 24 00:50:04 UTC 2008


The following reply was made to PR ports/128140; it has been noted by GNATS.

From: "Eric L. Chen" <lihong at ieee.org>
To: "Steve Ames" <steve at energistic.com>
Cc: bug-followup at freebsd.org
Subject: Re: ports/128140: update devel/pwlib to 2.4.1 to fit GNOME 2.24
Date: Fri, 24 Oct 2008 08:20:46 +0800

 On Thu, Oct 23, 2008 at 4:47 AM, Steve Ames <steve at energistic.com> wrote:
 >
 > Have you tested this pwlib update against other users of pwlib? I expect it will break openh323 which will break a number of other ports. I realize openh323 is pretty dated (the project forked into Opal and h323plus quite a while ago). However, I think introducing port breakage is to be avoided where possible. I believe there are only two direct consumers of pwlib in the source tree: Opal and openh323. The following ports all seem to go through the openh323 vector which will be broken by this upgrade to  pwlib:
 >
 > asterisk
 > asterisk-bristuff
 > asterisk-oh323
 > callgen323
 > cphone
 > gatekeeper
 > ohphone
 > openam
 > openmcu
 > versuch
 > yate-devel
 >
 > Most/All of them can be converted to Opal or H323Plus.
 >
 > Alternately you can create a new net/ptlib port and mark as conflicting conflicting with net/pwlib. Then update ptlib to 2.4.2 and set opal and company to use ptlib instead of pwlib. the upgrade path would be kind of hairy for people who already have pwlib installed but this may still be the easiest solution. I'm completely open to solutions, however the existing patch causes dependants to break and I'm not sure I have time to clean up after :)
 >
 > Some of these ports I'm not sure anyone cares about. Others (asterisk,gatekeeper,yate) people definately do.
 >
 
 I think create a new net/ptlib port is easier.



More information about the freebsd-ports-bugs mailing list