#51664: Please add pseudo-portnames for some common programs --------------------------+-------------------------------- Reporter: noloader@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by noloader@…): Replying to [comment:4 noloader@…]:
Replying to [comment:2 ryandesign@…]:
In the case of lcrypto, it does include the words "Bouncy Castle" in the long description, but not in the short description, and `port search` by default only searches the short description. You can get it to search the long description by passing a flag:
{{{ $ port search --long_description bouncy lcrypto @1.28 (java, crypto) Java cryptographic library }}}
but I admit this is not ideal. Maybe we should consider making `port search` also search the long description by default.
Yes, agreed. It would probably be better if things "just worked" out of the box without requiring the user to do extra things.
I was thinking about this earlier this evening. When I want to install a missing program, I usually type `{port|apt|yum|...} <program name>`. For example, `curl`, `wget`, `make`, `gmake`, `gcc`, `g++`, `clang`, `clang++`, `gdb`, `lldb`, etc. Perhaps the first step should be to add the common binary name rather than the long description? I think its important to keep extraneous noise to a minimum. Generally speaking, I *don't* want "depends" and "reverse depends" information showing up in my search results because it pollutes the results to the points they are nearly unusable for some packages. I fear a long description will do that sort of thing (my apologies if I am wrong). If I want dependencies or reverse dependencies, then I'll perform the package query with the appropriate switch. -- Ticket URL: <https://trac.macports.org/ticket/51664#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X