On 2014/07/08 19:16, Gustav Fransson Nyvell wrote: > On 07/08/14 19:12, Marc Espie wrote: > >On Tue, Jul 08, 2014 at 05:57:42PM +0100, Stuart Henderson wrote: > >>On 2014/07/08 18:54, Vadim Zhukov wrote: > >>>Hoping that /usr/sbin isn't full yet... This makes easier to get to > >>>package readme files: > >>> > >>> - Now you'll have exact command to view all added/changed readme > >>> files printed right after pkg_add(1) run; > >>> > >>> - You can simply type "pkg_readme mysql" if you're not sure what > >>> and where in MySQL you need to tweak, and still get there. > >>> > >>>kirby@ already liked it. Any more thoughts? > >>Couldn't this just be a subcommand of pkg_info? > >> > >>(Though personally I am pretty happy with "ln -s > >>/usr/local/share/doc/pkg-readmes /" ..) > >I have to agree with Stuart, I don't think it warrants a separate command. > >A bit at a loss about what switch to use though... > > > >Looks like pkg_info is bound to replace ls(1) in the infamous monty > >python joke. > > > pkg_search (made up) would be better to have. Finding a package and a > package you want, like maybe a new editor, a new compiler, can be very hard. > I usually go digging in /usr/ports but if you don't have or want ports on > your system I guess it might bug you. Maybe pkg_catalog or something. > Something very good and similar to browsing /usr/ports. --Gustav
You might like "pkg_add pkg_mgr"
