Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 289515

Summary: "equery list kde-base/" is not working
Product: Documentation Reporter: peng shao <shallpion>
Component: Project-specific documentationAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED INVALID    
Severity: trivial    
Priority: High    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
URL: http://www.gentoo.org/proj/en/desktop/kde/kde-config.xml
Whiteboard:
Package list:
Runtime testing required: ---

Description peng shao 2009-10-17 17:54:12 UTC
In code listing 4.2 it says

(List all the installed KDE packages)
# equery list kde-base/
(List all the installed KDE packages and select the ones from KDE 3.4)
# equery list kde-base/ | grep 3\.4

However for the recent version equery  it gives out 
 * Searching for  in kde-base ...
!!! Invalid Atom: 'kde-base/'

I guess it is a typo, or maybe used for an older version equery which I did not use..
Sorry if I made any mistake,

Reproducible: Always
Comment 1 Douglas Anderson 2009-10-20 17:47:55 UTC
Code listing 4.2 is correct for the stable version of equery in gentoolkit-0.2.4.5. In the unstable 0.3.0 branch of gentoolkit, equery now uses shell-like globbing. So you'll want to use:
$ equery list kde-base/*

equery list --help should explain the change, and a new man page will be released in rc8 soon.
Comment 2 peng shao 2009-10-20 18:51:53 UTC
(In reply to comment #1)
> Code listing 4.2 is correct for the stable version of equery in
> gentoolkit-0.2.4.5. In the unstable 0.3.0 branch of gentoolkit, equery now uses
> shell-like globbing. So you'll want to use:
> $ equery list kde-base/*
> 
> equery list --help should explain the change, and a new man page will be
> released in rc8 soon.
> 

Ok I see, sorry for the mis-reporting and thank you very much for the explanation:)

Comment 3 Wormo (RETIRED) gentoo-dev 2009-10-26 00:41:02 UTC
Thanks for the report, and thanks to Douglas for a prompt answer :)

Closing bug since it turned out to be an intentional syntax change rather than a bug.