Date: Mon, 18 Aug 2014 01:05:29 +0200 From: Matthias Andree <mandree@FreeBSD.org> To: marino@freebsd.org, Guido Falsi <madpilot@freebsd.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, owner-ports-committers@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r365208 - head/www/squidguard Message-ID: <53F13539.4050509@FreeBSD.org> In-Reply-To: <53F127D0.3060500@marino.st> References: <201408171718.s7HHIMRh017558@svn.freebsd.org> <9eead94ee58708b60a67fa030af7e2fc@secure.marino.st> <53F127D0.3060500@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 18.08.2014 um 00:08 schrieb John Marino: > Oh, and if that's not enough, squidguard is at risk of being removed > anyway because databases/db4, of which it depends, is unstaged and > getting removed. see: > > http://leaf.dragonflybsd.org/~marino/misc/screwed.maintained.txt Most stuff does not need much work to function with newer BerkeleyDB versions. <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192690>; has a patch that not only drops db4...db4.7 properly, but also move certain ports (albeit not squid stuff) onto newer db48/db5/db6, and if that goes through we'll make db5 the default. db6 has a stricter license (AGPL) so I'd not force it on the package builds. Sometimes you need to hack outdated configure scripts into shape, sometimes you only need to tell the port that it can work with newer versions, and sometimes you need to pull up the API changes and insert 0 or "" arguments into function calls. For the latter ports, you'll see complaining about mismatched argument types and count if you try forcing a newer BerkeleyDB on them. HTH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53F13539.4050509>