kmymoney2 package

schome1 · 2004-07-11 12:24:43

I have built a package for kmymoney2 - A financial manager (kmymoney2.sourceforge.net). I would like to either submit this package or request that it be included in the Arch package list. What would be easier?

fideli · 2004-07-12 15:15:46

http://bbs.archlinux.org/viewtopic.php?t=5347

i think submitting the package determines whether it will be in the arch package list, so it would be easier. what i did was put the PKGBUILD, filelist, and the final pkg in one tar file and uploaded it to ftp://ftp.archlinux.org/incoming . don't label it with "pkg.tar.gz" because it will look like an actual package, which it shouldn't be. i label mine with "madepkg" in it. i also made an entry at http://bliss-solutions.org/archlinux/incoming/index.php .

is your PKGBUILD different than mine? perhaps we can collaborate. let me know.

by the way, the above procedure is the conclusion i came up with after reading a few stickies and other posts in this forum. however, i'm a little concerned that there may be an overwhelming number of packages in incoming and i'd like to confirm with anyone out there if this is the right way of going about submitting a package. i'd also like to know if there's anything we submitters can do to ease the burden of maintaining packages for the maintainers.

Xentac · 2004-07-12 18:23:50

We're working on a new, hopefully, more efficient system.

http://www.archlinux.org/~jason/submission/

schome1 · 2004-07-13 02:22:52

This is what I had in my PKGBUILD file. The differences I saw were in the depends line, the makedepends, and the make line where I use DESTDIR. I had compiled this without the libxml2 and the libxml++ dependencies and it worked fine. Does it really need those files? Where and how do you find that out?

# Contributor: Mike Schommer <schome1@schome.net>

pkgname=kmymoney2
pkgver=0.6
pkgrel=1
pkgdesc="A personal finance manager for KDE"
url="http://kmymoney2.sourceforge.net"
license="GPL-2"
depends=('kdelibs>=3.0')
source=(http://umn.dl.sourceforge.net/sourceforge/kmymoney2/$pkgname-$pkgver.tar.bz2)
md5sums=('9cf0e358adb7756c0bf546155808e7ce')

build() {
  cd $startdir/src/$pkgname-$pkgver
  ./configure --prefix=/opt/kde
  make || return 1
  make DESTDIR=$startdir/pkg install
}

fideli · 2004-07-13 02:59:26

here's my PKGBUILD:

# Contributor: Faisal Moledina <fmoledina@uwaterloo.ca>
pkgname=kmymoney2
pkgver=0.6
pkgrel=1
pkgdesc="Personal finance manager for KDE"
url="http://kmymoney2.sourceforge.net/"
license="GPL-2"
depends=('kdelibs' 'libxml2')
makedepends=('libxml++')
source=(http://voxel.dl.sourceforge.net/sourceforge/kmymoney2/$pkgname-$pkgver.tar.bz2)
md5sums=('9cf0e358adb7756c0bf546155808e7ce')

build() {
  cd $startdir/src/$pkgname-$pkgver
  ./configure --prefix=/opt/kde
  make || return 1
  make prefix=$startdir/pkg/opt/kde install
}

we really only differ in the depends and makedepends, and also in the install prefix. i think libxml2 is a dependency for kmymoney2, and the c++ bindings for xml are needed during the build. if you install stuff in $startdir/pkg, doesn't it install in / when you install the package? i'm only asking because i don't know.

schome1 · 2004-07-13 03:45:05

I don't know either. I used DESTDIR because I copied it from another PKGBUILD (K3b) as an example. It worked, so I didn't bother changing it.

My build worked without the libxml2 dependencies.

I thought that I'd have to run pacman to install kmymoney after it was built, but I didn't. So now I'm not sure at all how the whole package build process works. From what I read, I thought it just build the packages in the directory where the PKGBUILD file was located, then you would run pacman -A package name to install it. Does that sound accurate to you?

fideli · 2004-07-13 10:36:30

that's how it should work. makepkg just builds the package in the dir, then you must run pacman -A in order to install it. i wonder how it just installed it automatically for you.

Xentac · 2004-07-13 18:53:15

It's because his PKGBUILD isn't correct and he built as root.

The application's build system installed the files where it was told to install them, to /. They actually installed there because root has write permission everywhere.

Next time use fakeroot and actually check the package that's created. Having a good understanding of how it all works helps to identify problems like this too.

Arch Linux

#1 2004-07-11 12:24:43

kmymoney2 package

#2 2004-07-12 15:15:46

Re: kmymoney2 package

#3 2004-07-12 18:23:50

Re: kmymoney2 package

#4 2004-07-13 02:22:52

Re: kmymoney2 package

#5 2004-07-13 02:59:26

Re: kmymoney2 package

#6 2004-07-13 03:45:05

Re: kmymoney2 package

#7 2004-07-13 10:36:30

Re: kmymoney2 package

#8 2004-07-13 18:53:15

Re: kmymoney2 package

Board footer