[MacPorts] #15434: RFE: port search should search name, description and long_description
#15434: RFE: port search should search name, description and long_description ---------------------------------+------------------------------------------ Reporter: raimue@macports.org | Owner: macports-tickets@lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | ---------------------------------+------------------------------------------ At the moment, port search only searches in the name of a port. It would be more helpful if it would also look in description and long_description. The result for 'port search foo' should be the same as for: {{{ port echo name:foo or description:foo or long_description:foo }}} (Given that we eliminate duplicates, #15433). -- Ticket URL: <http://trac.macports.org/ticket/15434> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@macports.org | Owner: raimue@macports.org Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Resolution: | Keywords: ----------------------------------+----------------------------------------- Changes (by raimue@macports.org): * owner: macports-tickets@lists.macosforge.org => raimue@macports.org * status: new => assigned -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@macports.org | Owner: raimue@macports.org Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Resolution: fixed | Keywords: ----------------------------------+----------------------------------------- Changes (by raimue@macports.org): * status: assigned => closed * resolution: => fixed Comment: Fixed in r37119. -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@macports.org | Owner: raimue@macports.org Type: enhancement | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Resolution: | Keywords: ----------------------------------+----------------------------------------- Changes (by landonf@macports.org): * status: closed => reopened * resolution: fixed => Comment: This actually makes 'search' pretty useless if you use a common term. Take 'tex' as an example -- port search tex returns 391 ports, but almost none of them are related to TeX. -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@macports.org | Owner: raimue@macports.org Type: enhancement | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Resolution: | Keywords: ----------------------------------+----------------------------------------- Comment (by raimue@macports.org): Replying to [comment:3 landonf@macports.org]:
This actually makes 'search' pretty useless if you use a common term. Take 'tex' as an example -- port search tex returns 391 ports, but almost none of them are related to TeX.
Hm, there is `port echo name:tex` to search in port names only, but that is not so obvious. How should it be changed? We could add flags to specify the fields to search for: {{{ port search tex port search --name tex port search --name --description --long_description tex }}} Or add an option to `port echo` to get more output than just the name. -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@macports.org | Owner: raimue@macports.org Type: enhancement | Status: reopened Priority: Normal | Milestone: MacPorts base enhancements Component: base | Version: 1.6.0 Resolution: | Keywords: ----------------------------------+----------------------------------------- Changes (by raimue@macports.org): * component: ports => base * milestone: => MacPorts base enhancements -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@macports.org | Owner: raimue@macports.org Type: enhancement | Status: reopened Priority: Normal | Milestone: MacPorts 1.7.0 Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ----------------------------------+----------------------------------------- Changes (by raimue@macports.org): * milestone: MacPorts base enhancements => MacPorts 1.7.0 Comment: Please comment what should be done here. I don't want to change the behavior again in the next release. -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@macports.org | Owner: raimue@macports.org Type: enhancement | Status: reopened Priority: Normal | Milestone: MacPorts 1.7.0 Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ----------------------------------+----------------------------------------- Changes (by blb@macports.org): * cc: blb@macports.org (added) Comment: The old search sometimes wasn't helpful because there are lots of things that should match but didn't because of the limits. The new one is somewhat the opposite, potentially giving too many results. I prefer the new way since to me more info is better, but some may disagree. The big problem here is that we don't really know how most people use search. One way to find out is to ship 1.7.0 with search like this and see if there are lots of tickets filed against it. If so, we can always switch back to the old method in 1.7.1 until a better solution is found. -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@… | Owner: raimue@… Type: enhancement | Status: reopened Priority: Normal | Milestone: MacPorts 1.7.0 Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ----------------------------------+----------------------------------------- Comment(by mcklaren@…): Replying to [comment:5 raimue@…]:
Replying to [comment:3 landonf@macports.org]:
This actually makes 'search' pretty useless if you use a common term. Take 'tex' as an example -- port search tex returns 391 ports, but almost none of them are related to TeX.
Hm, there is `port echo name:tex` to search in port names only, but that is not so obvious. How should it be changed?
We could add flags to specify the fields to search for: {{{ port search tex port search --name tex port search --name --description --long_description tex }}}
Or add an option to `port echo` to get more output than just the name.
I see fine this option, I think that port search tex could be a default form, for example, port search tex = port search --name tex then add 2 new options port search --description and port search --long-description, too i will add best a --long-description that --long_description, IMHO -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:9> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@… | Owner: raimue@… Type: enhancement | Status: reopened Priority: Normal | Milestone: MacPorts 1.7.1 Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ----------------------------------+----------------------------------------- Changes (by raimue@…): * milestone: MacPorts 1.7.0 => MacPorts 1.7.1 Comment: Moving to milestone 1.7.1, so we can revisit it again after 1.7.0 is released and we got some more feedback on 'port search'. -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@… | Owner: raimue@… Type: enhancement | Status: reopened Priority: Normal | Milestone: MacPorts 1.7.1 Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ----------------------------------+----------------------------------------- Comment(by andrew@…): This sort of search problem is rather common. My suggestion would be to add options for perl-like '''regular expression''' searching, as well as the --name, --description, and --long_description options. That way, if searching for TeX, you can use {{{ port search --rexexp "/\btex\b/i" }}} to search, case-insensitively, for TeX on a word boundary. Just my $0.02 - and at the current Canada to US exchange rate, it may not be worth much... :-) -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:11> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@… | Owner: raimue@… Type: enhancement | Status: reopened Priority: Normal | Milestone: MacPorts 1.7.1 Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ----------------------------------+----------------------------------------- Comment(by clayton@…): I would agree that the new search can be helpful but it is bringing back way to much information. Another example is the ack (p5-app-ack) port. {{{ $ port search ack ... Found 673 ports. }}} That more than fills up the buffer on my terminal :). I like the idea of having the options for searching --name, --description and --long- description. I'm inclined to say that it should search --name by default also. -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:12> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@… | Owner: raimue@… Type: enhancement | Status: reopened Priority: Normal | Milestone: MacPorts 1.7.1 Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ----------------------------------+----------------------------------------- Comment(by raimue@…): I added some new options to `port search` on trunk, check `port help search` to see them all. Special options are now --exact, --glob, --regex to choose match style; --case-sensitive should be obvious. The other options specify which fields are searched. Relevant revisions are r44071, r44073, r44077, r44079, r44080, r44082, r44083, r44084. -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:13> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@… | Owner: raimue@… Type: enhancement | Status: closed Priority: Normal | Milestone: MacPorts 1.8.0 Component: base | Version: 1.6.0 Resolution: fixed | Keywords: Port: | ----------------------------------+----------------------------------------- Changes (by raimue@…): * status: reopened => closed * resolution: => fixed * milestone: MacPorts 1.7.1 => MacPorts 1.8.0 Comment: Moving to 1.8.0 as this also includes some refactoring parts. -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:14> MacPorts <http://www.macports.org/> Ports system for Mac OS
#15434: RFE: port search should search name, description and long_description ----------------------------------+----------------------------------------- Reporter: raimue@… | Owner: raimue@… Type: enhancement | Status: closed Priority: Normal | Milestone: MacPorts 1.8.0 Component: base | Version: 1.6.0 Resolution: fixed | Keywords: Port: | ----------------------------------+----------------------------------------- Comment(by raimue@…): The default was changed in r48007 to `port search` being equivalent to `port search --name --description`, which gives much better results for some search terms, e.g. "haskell". If this gives too much results, it can be narrowed down with the new options. -- Ticket URL: <http://trac.macports.org/ticket/15434#comment:15> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts