Date: Sun, 6 Jul 2014 20:56:23 +0200 From: Tijl Coosemans <tijl@FreeBSD.org> To: Kurt Jaeger <pi@FreeBSD.org> Cc: ports@freebsd.org Subject: Re: upgrade to security/libgcrypt, shared lib bump, what needs to be done ? Message-ID: <20140706205623.2288c2d5@kalimero.tijl.coosemans.org> In-Reply-To: <20140706205203.4176600e@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 6 Jul 2014 20:52:03 +0200 Tijl Coosemans wrote: > On Sun, 6 Jul 2014 19:48:59 +0200 Kurt Jaeger wrote: >> I prepared a new diff, see >> >> http://people.freebsd.org/~pi/misc/libgcrypt.svndiff-v2 >> >> Can you have a look at it, before I mess up the whole tree 8-} ? > > net/samba4/Makefile: PORTREVISION messed up > net/samba41/Makefile: PORTREVISION messed up > security/libgcrypt/Makefile: Keep post-patch silent maybe? > > Looks good otherwise, so go ahead and commit There's no major incompatibility with the old version of libgcrypt right? Have you tried to compile some of the ports that depend on libgcrypt to see if nothing breaks?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140706205623.2288c2d5>