You are not logged in.
Pages: 1
Hello people,
As many of you might have noticed, Shaman in community is getting more and more unstable each pacman update. It should not come as a news that the current Shaman is becoming almost unmaintainable and there's not much that can be done about it. Those of you reading Planet KDE might have read my post about Shaman 2, those of you who don't might check it out here: drfav.wordpress.com/2009/12/01/introducing-shaman-a-new-universal-package-management-frontend. Don't get yourself fooled by the fact that it's "universal": it has first class native Arch support (so without packagekit, also because PK on arch is completely unusable), and will soon replace Shaman 1.
It depends on kdelibs. Just don't get mad about this, the new Shaman has an extremely solid and complex architecture underneath that needed a superior framework to Qt. To my view, we're almost to the point where Shaman 2 outperforms Shaman 1 in terms of speed and reliability. To compile it, you need aqpm from git (http://git.chakra-project.org/tools/aqpm) and of course Shaman from subversion. It is in KDE svn, here: http://websvn.kde.org/trunk/playground/sysadmin/shaman/ . Since the executable is named "shaman", you might want to remove Shaman 1 first if you're installing Shaman 2.
P.S.: You actually need to install it, since it relies on plugins, icons and stuff. And run kbuildsycoca4 right after so you don't have to wait 2 additional minutes
Testing and impressions are more than welcome
Offline
You really should copy over stuff like this to the pacman-dev ML.
Good luck with your work.
Offline
It depends on kdelibs. Just don't get mad about this
Can't imagine why anyone would, seeing as kde users are the most likely shaman users.
Good luck with it anyway.
Offline
Pages: 1