James wrote:
> Hello,
>
> qpkg is not accessible, due to the path, unless
> I use: /usr/lib/gentoolkit/bin/qpkg
>
> Where is the best (bash shell) place to
> set this path once, so I do not have to
> type out the fully qualified pathname
> of the executable?
> I'd like it to survive the machinations of
> emerge, env-update et. al...
>
> /root/.bashrc ?
>
> I also would have thought that installing it
> from an emerge would set the path automatically?
>
>
why not to do a litle jump and go with app-portage/portage-utils ?
#q --help
Usage: q <applet> [arguments]...
Currently defined applets:
q <applet> <args> : virtual applet
qcheck <pkgname> : verify mtimes/digests
qdepends <pkgname> : show dependency info
qfile <filename> : list all pkgs owning files
qgrep <misc args> : grep in ebuilds
qlist <pkgname> : list files owned by pkgname
qlop <pkgname> : emerge log analyzer
qpkg <misc args> : manipulate Gentoo binpkgs
qsearch <regex> : search pkgname/desc
qsize <pkgname> : calculate size usage
qtbz2 <misc args> : manipulate tbz2 packages
quse <useflag> : find pkgs using useflags
qxpak <misc args> : manipulate xpak archives
Options: -[irvQChV]
-i, --install * Install symlinks for applets
-r, --reinitialize * Reinitialize ebuild cache
-v, --verbose * Make a lot of noise
-Q, --quiet * Suppress warnings and errors
-C, --nocolor * Don't output color
-h, --help * Print this help and exit
-V, --version * Print version and exit
cheers,
Francesco R:
--
[email protected] mailing list
