freebsd-ports/www/squid31/pkg-descr

Squid is a high-performance proxy caching server for web clients,
supporting FTP, gopher, and HTTP data objects. Unlike traditional
caching software, Squid handles all requests in a single, non-blocking,
I/O-driven process.

Squid supports SSL, extensive access controls, and full request logging.
By using the lightweight Internet Cache Protocol, Squid caches can be
arranged in a hierarchy or mesh for additional bandwidth savings.

WWW: http://www.squid-cache.org/
- update pkg-descr and remove some cruft - consistently use "Squid" when referring to the software's name - define COMMENT a bit less chatty - replace the progeny.com mirror with the one hosted by Vistech - fix a wrong path in pkg-message.in (thanks to "Tuc at the Beach House") - pass ${squid_flags} when stopping or reconfiguring Squid (ports/100510) PR: ports/105023 Submitted by: Thomas-Martin Seck <tmseck@netcologne.de> (maintainer) Sponsored by: FreeBSD Bug-a-thon #2 2006-11-05 00:03:40 +01:00			`Squid is a high-performance proxy caching server for web clients,`
			`supporting FTP, gopher, and HTTP data objects. Unlike traditional`
			`caching software, Squid handles all requests in a single, non-blocking,`
			`I/O-driven process.`

			`Squid supports SSL, extensive access controls, and full request logging.`
			`By using the lightweight Internet Cache Protocol, Squid caches can be`
			`arranged in a hierarchy or mesh for additional bandwidth savings.`
- configure squid to run under a dedicated "squid" user by default; make use of SQUID_{UID,GID} which other squid-related ports already implemented. The user/group will be created on the fly if they do not already exist. - introduce WITH_SQUID_LDAP_AUTH to pull in the necessary bits to compile and use the ldap_auth helper - install some more authentication helper applications by default - install helper applications to ${PREFIX}/libexec/squid instead of ${PREFIX}/libexec, add notes about it in pkg-install and pkg-descr - cleanup the pre-installation tasks and move them from Makefile and pkg-plist into the pkg-install script; make 'make install' and 'pkg_add' actually do the same thing - introduce a pkg-deinstall script - make squid.sh rcNG compatible (when either /etc/rc_subr or ${PREFIX}/etc/rc_subr is present, the first one will be used, otherwise the script will work as a "rc classic" script so no additional dependency on the rc_subr port should be needed) - some Makefile cleanups: + the squid installation procedure now correctly strips binaries, so there is no need to do this manually anymore + generate those parts of pkg-plist dynamically that may be affected by user set tunables (currently the localized error pages and helper applications) + document the available configuration options in a slightly different style + remove some obsolete variable declarations and comments + honor NOPORTDOCS - add CONFLICTS - add another vendor patch, see http://www.squid-cache.org/bugs/show_bug.cgi?id=890 for a thorough explanation of what has been fixed. - since we can no longer take the presence of Lithuanian error pages for granted, wrap the workaround for the errorpages.patch with '.if exists()' - bump PORTREVISION PR: 61315 Submitted by: maintainer 2004-01-16 22:18:20 +01:00
PR: 26059 Update the squid-2.4 port to actually _be_ squid-2.4 . Phew. This port builds, installs, packages, pkg_delete's cleanly. I'm going to run it through some more linting and tidying up before I'm completely done with it. Differences from squid22/squid23 : * install-pinger isn't built. I'll tackle this later, possibly by creating a squid user/group. I don't like having suid binaries installed, even more so when 99% of the users of this port won't even enable ICMP pinging. * I've enabled the lru and heap replacement policies. LRU is used by default, the beauty here is that the user can choose one or the other without needing a recompile. * I've enabled ufs (sync), diskd (async) and null (no caching, only proxying). This again lets users choose what they want without needing a recompile. The default is still a 100mb cache in /usr/local/squid/cache/ running ufs. I would change it to diskd but if the user hasn't tweaked their sysV shm/msg parameters sufficiently they'll just be puzzled when squid gives mysterious sysV errors (and if they load it up enough to have UFS become an issue, they'd be better off reading the squid FAQ anyhow..) 2001-03-27 14:28:47 +02:00			`WWW: http://www.squid-cache.org/`