cvs commit: src/usr.sbin/pkg_install
pkg_info.1 src/usr.sbin/pkg_install/search Makefile pkg_search.1 ...
delphij at delphij.net
Mon Dec 10 11:23:17 PST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Doug Barton wrote:
> 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.
Let's see what we can do it in the future: teach pkg_search about how to
download an INDEX file for use, something that you don't have to install
the whole ports tree and can do easily.
I think this is a very useful feature. There are a lot of users who use
packages rather than using ports, and something like pkg_search,
pkg_update would definitely be an useful add to our current package tool
Xin LI <delphij at delphij.net> http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
-----END PGP SIGNATURE-----
More information about the cvs-src