Date: Wed, 22 Oct 2008 21:30:04 GMT From: Steve Ames <steve@energistic.com> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/128140: update devel/pwlib to 2.4.1 to fit GNOME 2.24 Message-ID: <200810222130.m9MLU4WO060683@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/128140; it has been noted by GNATS. From: Steve Ames <steve@energistic.com> To: bug-followup@FreeBSD.ORG Cc: d9364104@mail.nchu.edu.tw Subject: Re: ports/128140: update devel/pwlib to 2.4.1 to fit GNOME 2.24 Date: Wed, 22 Oct 2008 16:47:20 -0400 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 pw lib: 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200810222130.m9MLU4WO060683>