about the name, since i'm not really work on it any more and my pakman can only run on FW i dont see any reason why shouldnt u use the name pakman.
one last thing about my pakman, i actually done some nice work with it and i encourege u to try it out on FW, it is doing the job so fast that it's really a joy to work with it, u can enable disable repos on the fly even without the need to refreash, it features a system tray icon and some nice informative splash screen, and there is some really nice colorfull loging dialog that appears after any actions if the user check the loging option.
some Q i would like to know about your work, do u use libalpm to do the task or pacman?
]]>At the bottom it says "founded 2509 packages", I think it's supposed to be "found"?
]]>I'm sorry for the pacman's configuration file rewriting. I've tested it on my system and it don't give me any problem.
pakman need to rewite config file because pacman.conf doesn't respect a KDE configuration file format editable thru KConfig class of KDE's libraries. In pacman.con there are some duplicated entries for NoUpgrade entries and KConfig clas read only the last entry. So paKman try to rebuld pacman.conf without duplicates but, evidently, there are something wrong . :cry:
arooaroo's idea is very good. paKman could be save a pacman's configuration file copy changed by user in $HOME/.kde/share/apps/paKman/pacman.conf and use --config option when invoke pacman.
May be a good solution?
This is the original /etc/pacman.conf content (if someone want restore it after paKman's changes)
#
# /etc/pacman.conf
#
# NOTE: If you find a mirror that is geographically close to you, please
# move it to the top of the server list, so pacman will choose it
# first.
#
# To re-sort your mirror lists by ping/traceroute results, use the
# /usr/bin/sortmirrors script. It requires the "netselect" package.
#
# See the pacman manpage for option directives
#
# GENERAL OPTIONS
#
[options]
LogFile = /var/log/pacman.log
NoUpgrade = etc/passwd etc/group etc/shadow etc/sudoers
NoUpgrade = etc/fstab etc/raidtab etc/ld.so.conf
NoUpgrade = etc/rc.conf etc/rc.local
NoUpgrade = etc/modprobe.conf etc/modules.conf
NoUpgrade = etc/lilo.conf boot/grub/menu.lst
HoldPkg = pacman glibc
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here.
# - local/custom mirrors can be added here or in separate files
#
#[testing]
#Server = ftp://ftp.archlinux.org/testing/os/i686
[current]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/current
[extra]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/extra
#[unstable]
# Add your preferred servers here, they will be used first
#Include = /etc/pacman.d/unstable
#[community]
# Add your preferred servers here, they will be used first
#Include = /etc/pacman.d/community
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#Server = file:///home/custompkgs
I think it's possible to save these settings in their own preferences file, and them use them with the various pacman arguments.
So, rather than overwriting the IgnorePkg field, just store packages to ignore somewhere and when you call pacman, use --ignore arguments, for example.
]]>I have tried your app...
From the design point of view:
Very nice gui,i like it very much
From the technical point of view:
It has messed up my pacman.conf... Before i had a standard non-altered pacman.conf, and your app rewrote it and i had some errors with the repos, something like that the database for current can not be found... So why does it rewrite that file? Maybe it could just read the settings from it...
Anyway, this app looks very promising to me and i will keep an eye on it, keep up the good work
]]>Does anyone else think the pacman dependency is implicit?
Yes, the paman dependency can be removed.
Also the pkgrel is misused. It is supposed to be the version of the PKGBUILD and should be equal to 1 here. Here's a corrected PKGBUILD:
pkgname=pakman
pkgver=0.1
pkgrel=1
pkgdesc="KDE gui frontend for pakman packages manager."
url="http://www.brainspace.it/"
license="GPL"
depends=(kdelibs)
source=(http://www.brainspace.it/files/$pkgname-$pkgver-beta1.tar.bz2)
md5sums=(b90fb88e19a04c03b30fb0819b8fa7aa)
build() {
cd $startdir/src/$pkgname-$pkgver-beta1
./configure
make || return 1
make DESTDIR=$startdir/pkg install
}
pkgname=pakman
pkgver=0.1
pkgrel=beta1
pkgdesc="KDE gui frontend for pakman packages manager."
url=""
license="GPL"
depends=(kdelibs pacman)
makedepends=()
conflicts=()
replaces=()
backup=()
install=
source=(http://www.brainspace.it/files/$pkgname-$pkgver-$pkgrel.tar.bz2)
md5sums=(b90fb88e19a04c03b30fb0819b8fa7aa)
build() {
cd $startdir/src/$pkgname-$pkgver-$pkgrel
./configure
make || return 1
make DESTDIR=$startdir/pkg install
}
Good work, although there are now 2 C++/KDE pacman frontends that have just started and it seems like a good idea to collaborate.
It is the best way, for me.
Another thing to do, is a svn ( or cvs ) repo: the developers can made modify and share it with the community. But of this we have just talked
For the modify, you can use a combination of find / grep / awk + regular expression.
Regards
]]>That said, I think you could streamline your interface a bit. The "buttons" are very large because they contain a long description. These could be moved in to tooltips, for example. Also, I think the Ignore Packages looks a bit awkward and it's location in the Control Center doesn't seem obvious to me on first glance.
Good work, although there are now 2 C++/KDE pacman frontends that have just started and it seems like a good idea to collaborate.
]]>