On Thu, 15 Dec 2005 13:26:47 -0600, Paul Varner wrote:
> > Because it doesn't appear to offer features that qpkg does, for
> > example; listing all installed packages in a particular category
> >
> > qpkg -I -g kde-base
>
> Actually it does:
>
> qlist -I kde-base
>
> Will show all installed pa
On Thu, 2005-12-15 at 19:12 +, Neil Bothwick wrote:
> On Thu, 15 Dec 2005 18:11:04 +0100, Francesco Riosa wrote:
>
> > why not to do a litle jump and go with app-portage/portage-utils ?
>
> Because it doesn't appear to offer features that qpkg does, for example;
> listing all installed packag
On Thu, 15 Dec 2005 18:11:04 +0100, Francesco Riosa wrote:
> why not to do a litle jump and go with app-portage/portage-utils ?
Because it doesn't appear to offer features that qpkg does, for example;
listing all installed packages in a particular category
qpkg -I -g kde-base
--
Neil Bothwick
On Thu, 15 Dec 2005 10:56:30 -0600, Paul Varner wrote:
> My recomendation is to create a symbolic link in /usr/local/bin (which
> is in the default path)
That doesn't work with gentoolkit-0.2.1*, because qpkg is now
in /usr/share/doc/$PF/deprecated/qpkg/qpkg, so an upgrade of gentoolkit
would bre
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 machinatio
On Thu, 2005-12-15 at 16:22 +, James wrote:
> 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
On Thu, 15 Dec 2005 16:22:16 + (UTC), James wrote:
> 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
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. a
8 matches
Mail list logo
