in waiting for the next release, thanx for the answers
]]>But anyway, it's all in the works, so let's just wait for the next pacman release.
]]>pacman -Q | grep kde
only lists packages with kde in the name.
Hapy.
]]>Kritoke
]]>But how getting the current package list
abs
then running
cd /usr/abs/kde
pacman -R `/bin/ls`
I am used a similar method to install Gnome.
abs
cd /usr/abs/gnome
pacman -S `/bin/ls`
From the ChangeLog itself:
Added group handling, so one can run 'pacman -S kde' and
install all files from the KDE group
Not sure about the other things though, those sound like some very good ideas that should be considered and hopefully they aren't too hard to implement.
Kritoke
]]>here the problem that brings me to this idea:
say i want to remove kde
-> what you have now to do: pacman -R kde{???}, well no actually you have first to go to the internet and have a search in the package-section to find out what packages are part of kde (kdebase, kdelibs ...)
here the idea:
what about being able to simply type
pacman -Q kde*
to find out what kde packages are installed on your system ... and futuremore being able to do also
pacman -R kde* #to remove all kde packages
#or
pacman -Rc kde* #to remove all kde and other related to kde packages
the same would be also cool for installing packages
->just to show you what happens now in pacman:
pacman -Q gnome*
Package "gnome*" was not found.
what do you think?
]]>