Date: Sun, 16 Dec 2012 18:47:38 GMT From: Joel Rodriguez <joel@tahoestores.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/174488: rebuild of pcre breaks too many things Message-ID: <201212161847.qBGIlcnl066557@red.freebsd.org> Resent-Message-ID: <201212161850.qBGIo0la066009@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 174488 >Category: ports >Synopsis: rebuild of pcre breaks too many things >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Dec 16 18:50:00 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Joel Rodriguez >Release: FreeBSD 9.0-RELEASE (GENERIC) #0 >Organization: Gossamer >Environment: FreeBSD tahoestores.net 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.\ edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: The update for pcre deleted libpcre.so.1 and installed libpcre.so.3. Of course, the build did not mention this and of course, this breaks anything and everything that depends on pcre, which is a lot. No, don't go telling me to use ldd because we all know that it is next to impossible to identify what to rebuild based on the binaries. This is absurd. What am I suppose to do? Rebuild everything? I am sure the developers had a good reason to rename the so, but if they want to do so then they should provide a tool to identify everything that needs to be rebuilt. While I am picking on the pcre staff, this happens anytime a development team ups their revision number on a so. Hey guys, these are shared objects!!!!!!!!!! Give me a fricken break. >How-To-Repeat: That should be obvious. >Fix: Provide a tool to identify what to rebuild, hopefully in the Makefile. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201212161847.qBGIlcnl066557>