Date: Fri, 24 Oct 2008 02:40: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: <200810240240.m9O2e4UR008413@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: "Eric L. Chen" <lihong@ieee.org> Cc: bug-followup@freebsd.org Subject: Re: ports/128140: update devel/pwlib to 2.4.1 to fit GNOME 2.24 Date: Thu, 23 Oct 2008 22:34:21 -0400 On Fri, Oct 24, 2008 at 08:20:46AM +0800, Eric L. Chen wrote: > > 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. Agreed. You'd just need to put some thought into the upgrade path for people who already have pwlib installed. This may be especially true for people who use packages instead of building from source... unless you can get the two (pwlib and ptlib) to co-exist? With ptlib in the tree we could invite maintainers to switch their ports from openh323 to opal and then remove openh323 and pwlib from the tree entirely.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200810240240.m9O2e4UR008413>