Upstream releases stable patched versions as well as beta and patched beta versions. I'm attaching a patch for the latest Gentoo squid ebuild to support these versions. I'm not sure the ebuild file name format for _p is correct but it "works for me". The problem is that even if the official Gentoo docs state that it should be _pYYYYMMDD, the upstream release cycle can be faster and one can find more than one revision on the same day. The advantage of applying the ebuild patch I propose is that you can then simply copy the following files: squid-3.5.23_p2016122614129.ebuild squid-4.0.17_beta.ebuild squid-4.0.17_beta_p2017012214968.ebuild and you can emerge any one of: squid-3.5.23-20161226-r14129 squid-4.0.17 squid-4.0.17-20170122-r14968 I'm also attaching the FILESDIR gentoo patch for Squid 4.
Created attachment 461140 [details, diff] gentoo patch file in FILESDIR
Created attachment 461142 [details, diff] squid ebuild patch
Created attachment 496994 [details, diff] patch to be applied to squid 3.5.26 ebuild Upstream has changed the file format. So now I'm attaching a new proposal. It's a simple patch for the 3.5 ebuild. Known to work for squid 3.5.27 and 3.5.26. Will not propose Squid 4 for now. The patch relies on a new init script which can be found here: https://bugs.gentoo.org/629066
Please take a look at this bug report too: https://bugs.gentoo.org/629066
I am not enthusiastic about squid betas at all.
