qsearch doesn't understand DESCRIPTIONs that contain linebreaks. An example for a package with a linebreak in DESCRIPTION is b43-fwcutter (and many more. A little find/grep combo counted about 180). The worst thing about this bug is that qsearch doesn't just take the 1st line of the DESCRIPTION, it ignores the complete package. This means that qsearch -s b43-fwcutter will return no results. Reproducible: Always Steps to Reproduce: qsearch -s b43-fwcutter Actual Results: <no output> Expected Results: net-wireless/b43-fwcutter Firmware Tool for Broadcom 43xx based wireless network devices using the mac80211 wireless stack or at least net-wireless/b43-fwcutter Firmware Tool for Broadcom 43xx based wireless network devices (i.e. the 1st line of the description)
Are newlines really allowed in DESCRIPTION? If so, shouldn't the cache files be generated with them replaced with a space, like with HOMEPAGE?
(In reply to comment #1) > Are newlines really allowed in DESCRIPTION? Hmmm? man bash /IFS <snip> IFS The Internal Field Separator that is used for word splitting after expansion and to split lines into words with the read builtin command. The default value is ‘‘<space><tab><newline>’’. </snip>
CACHE_METADATA is now default for qsearch. A new option(-e) was added for the fallback method of using CACHE_EBUILD
