Unless the shareable version number is bumped, there is no need to
re-build dependent ports. Most updates to shareables do not change the
API or ABI, so dependent packages simply pull in the updated shareable
when they load. You should only have to do the mass update once,
whether for 1.5.10
What is the current status of newly-released png-1.5.11?
My main concern is having to portupgrade/portmaster all ports that have png as
a dependency,
don't want to have to do this for png-1.5.10 and then a day or two later for
png-1.5.11.
Maybe NetBSD pkgsrc promptly updated png to 1.5.11
On Tue, Jun 19, 2012 at 2:21 AM, Thomas Mueller muelle...@insightbb.com wrote:
What is the current status of newly-released png-1.5.11?
My main concern is having to portupgrade/portmaster all ports that have png
as a dependency,
don't want to have to do this for png-1.5.10 and then a day or
While checking the new packages/ports in NetBSD pkgsrc and FreeBSD ports, I
noticed png-1.5.11 just added in NetBSD pkgsrc, which is usually behind FreeBSD
ports, but not yet in FreeBSD ports (just ran portsnap fetch update).
Not to be unduly impatient, but I don't want to upgrade a whole lot
