public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Francesco Riosa <BastianBalthazarBux@pnpitalia.it>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  setting path for qpkg
Date: Thu, 15 Dec 2005 18:11:04 +0100	[thread overview]
Message-ID: <43A1A3A8.1000807@pnpitalia.it> (raw)
In-Reply-To: <loom.20051215T171715-802@post.gmane.org>

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:
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-12-15 17:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15 16:22 [gentoo-user] setting path for qpkg James
2005-12-15 16:48 ` Neil Bothwick
2005-12-15 18:00   ` [gentoo-user] " James
2005-12-15 16:56 ` [gentoo-user] " Paul Varner
2005-12-15 18:14   ` [gentoo-user] " James
2005-12-15 19:11   ` [gentoo-user] " Neil Bothwick
2005-12-15 17:11 ` Francesco Riosa [this message]
2005-12-15 18:27   ` [gentoo-user] " James
2005-12-15 19:12   ` [gentoo-user] " Neil Bothwick
2005-12-15 19:26     ` Paul Varner
2005-12-15 20:08       ` [gentoo-user] " James
2005-12-15 20:56         ` Francesco Riosa
2005-12-15 21:52         ` Paul Varner
2005-12-15 21:45       ` [gentoo-user] " Neil Bothwick
2005-12-15 23:01       ` Peter Ruskin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43A1A3A8.1000807@pnpitalia.it \
    --to=bastianbalthazarbux@pnpitalia.it \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox