| Summary: | www-client/surfraw-2.2.8 version bump. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | James Rowe <jnrowe> |
| Component: | New packages | Assignee: | Jeroen Roovers (RETIRED) <jer> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | surfraw-2.2.8-version_bump.patch | ||
Created attachment 279863 [details, diff]
surfraw-2.2.8-version_bump.patch
@jer when you bump please add die after sed and do* functions or bump to eapi4 If you have time/hw test also if works emake in src_install ;) Thanks. It's in with some more minor changes. |
surfraw 2.2.8 has been released! New features include: * Stack of new elvis, include `bugzilla` that can be used on the Gentoo installation * Many fixes to existing elvis * Support for opensearch without all the perl modules There is one possible problem, and I'm not sure how it should be dealt with. The opensearch support works by hitting http://erislabs.net/ianb/webtools/opensearch and letting it build the search query. Obviously this lets Ian(surfraw's awesome maintainer) access the searches that a user submits, and I wonder if there should at least be a note in the pkg_postinst¹ about the possibly unexpected information leakage? I'll note that Opera does a similar thing with many of its default searches, and there is no user note for that behaviour in the ebuild. Thanks, James ¹ Yes, in the already stupidly huge pkg_postinst notes. Reproducible: Always