Date: Sun, 6 Jul 2014 21:53:50 +0200 From: Kurt Jaeger <pi@FreeBSD.org> To: Tijl Coosemans <tijl@FreeBSD.org> Cc: ports@freebsd.org, Kurt Jaeger <pi@FreeBSD.org> Subject: Re: upgrade to security/libgcrypt, shared lib bump, what needs to be done ? Message-ID: <20140706195350.GE73593@f10.opsec.eu> In-Reply-To: <20140706214308.7156373d@kalimero.tijl.coosemans.org> References: <20140706111643.GB73593@f10.opsec.eu> <20140706145604.0483ae7f@kalimero.tijl.coosemans.org> <20140706174859.GC73593@f10.opsec.eu> <20140706205203.4176600e@kalimero.tijl.coosemans.org> <20140706205623.2288c2d5@kalimero.tijl.coosemans.org> <20140706192720.GD73593@f10.opsec.eu> <20140706214308.7156373d@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > >> Have you tried to compile some of the ports that depend on libgcrypt > >> to see if nothing breaks? > > > > No, due to number of ports involved (104), list at > > http://people.freebsd.org/~pi/misc/libgcrypt-related-ports [...] > > For this we probably need some exp-run ? > It's safer to do an exp-run. Then the PR is on it's way to portmgr for an exp-run now 8-} -- pi@FreeBSD.org +49 171 3101372 6 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140706195350.GE73593>