Date: Tue, 19 Aug 2014 11:31:56 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 192828] New: add squid34 to ports Message-ID: <bug-192828-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192828 Bug ID: 192828 Summary: add squid34 to ports Product: Ports Tree Version: Latest Hardware: amd64 OS: Any Status: Needs Triage Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: timp87@gmail.com Created attachment 146026 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146026&action=edit squid34 port dir An attempt to make a port for squid34. It's stable and the only one supported by upstream version of squid. It's based on existing www/squid33 and port made by Dennis Glatting. I know, it's a mess in PLIST_FILES, but it's the first step. I plan to convert it to normal pkg-plist format in future, but not now. I checked and tried every option. FS_COSS and ECAP don't build. Don't know how to fix it. Marked as broken. Others are ok and they are staging without any problems. No more "WARNING: no_suid: setuid(0): (1) Operation not permitted" messages in logs (thanks to the www/squid33). What's the difference between www/squid33? - latest squid-3.4.6 with latest patches. - more files in SHEBANG_FILES. - reorder a bit PLIST_FILES stuff + honor SSL. - add squid_krb5_ktname to rc.d script. Hope someone else will test it and maybe provide a patch to fix 2 broken oprions. P.S. Maybe it should be at www/squid, not in www/squid34? -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192828-13>