| Summary: | if recipe = git, 18 pages shown | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Layer Index | Reporter: | Armin Kuster <akuster> |
| Component: | Layer Index Metadata | Assignee: | Elliot Smith <elliot.smith> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bluelightning, brian.avery, sgw |
| Version: | unspecified | ||
| Target Milestone: | 2.2 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Armin Kuster
2016-02-24 00:56:32 UTC
It's matching on the filename in this case. Armin, could you please supply more details about exactly where this issue occurs (which search input you're using), and what you would expect to see in the results (roughly) as compared to what you're actually seeing? Thanks. It's the search box on the recipes page which leads you to: http://layers.openembedded.org/layerindex/branch/master/recipes/?q=git (In reply to comment #2) > Armin, could you please supply more details about exactly where this issue > occurs (which search input you're using), and what you would expect to see > in the results (roughly) as compared to what you're actually seeing? > > Thanks. All I wanted it to see the "git" recipe. not all recipes with "git" in them. 18 pages of stuff is a lot to weed through. maybe we need an option for 'exact' match so only what we type in the box is what is shows. I realize "git" is the worst offender. if we ever have a package named "BB" we are in trouble ( 167 pages ;) ) This can be resolved by changing calls to simplesearch.get_query() so that only the "name" or "pn" field is used for the search (depending on where the search is happening). Is this an acceptable fix? I looked at this again and decided I should leave the machine search matching against name and description; recipe searches will only match pn. I can't recall the examples, but I think I was searching also the filename to catch recipes for which PN doesn't contain the string you'd be searching for (was it skipped recipes? I'm not sure; I'd have to go digging). It could be that we care less about those than not flooding the results with garbage though and we can address minor fallout later. Now deployed to the live site. |