Summary: | net-proxy/squid-5.0.4 (beta) version bump | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Vieri <rentorbuy> |
Component: | Current packages | Assignee: | Mikle Kolyada (RETIRED) <zlogene> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | hydrapolic |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
a patch for the squid v5 ebuild
modified patch in filesdir just to show the diff between files |
Description
Vieri
2020-10-07 13:20:51 UTC
Created attachment 665566 [details, diff]
a patch for the squid v5 ebuild
Ebuild patch for Squid 5.0.4
Created attachment 665569 [details, diff]
modified patch in filesdir
Of course it should be renamed to contain 5.0.4 or simply "5" and preserve the current file for Squid 4.3.
Created attachment 665572 [details, diff]
just to show the diff between files
Squid 5.0.4 builds and installs fine with these changes. There are important features in Squid 5 that are not backported to Squid 4 so it would be great to have it in Portage. Rather not, betta is still buggy and I do not want to pull our users into it. I'm not sure Squid 5 actually has more severe bugs than Squid 4. In any case, I find that the fact that Squid 4 doesn't support websockets is a major drawback these days compared to Squid 5 (which works fine with websockets). Anyway, it's your call. I can still use the custom ebuild -- no problem at all. It's just that historically Squid 4 has been in beta status for a *very* long time even though it was rather stable. Time will tell if Squid 5 will go the same route. Thanks BTW, users are not forced to install Squid 5 if Squid 4 is marked stable unless they want to. Besides, Gentoo has always been a bleeding edge distro. Just my 2 cents. |