cvs commit: src/usr.sbin/pkg_install Makefile src/usr.sbin/pkg_install/add pkg_add.1 src/usr.sbin/pkg_install/create pkg_create.1 src/usr.sbin/pkg_install/delete pkg_delete.1 src/usr.sbin/pkg_install/info pkg_info.1 src/usr.sbin/pkg_install/search Makefile pkg_search.1 ...

[Doug Barton]

David O'Brien wrote:

> We owe it to our users to make it easy to add or install a port.  In
> order for a user to do that, they need to know the name (if pkg_add -r),
> or location (if building themselves).  That is the problem pkg_search
> solves.  In fact someone told me about a new port I would find useful.
> In the end they gave me the wrong path to where it lives in /usr/ports
> and it took more effort than it should have to figure out where it lives.
> With pkg_search (in the base system) it would have taken only a second.

You can accomplish the same thing by doing:
cd /usr/ports
make search name=blah

Note, I'm not commenting on the value of the pkg_search tool, or the
worth of including it in the base, or anything else other than to say
that what you want to do is already possible, and fairly well documented.

hth,

Doug

-- 

    This .signature sanitized for your protection