You are not logged in.
Hi there, I just wanted to give xfburn a try, but i recognized that it was not in the repos. So i tried writing a PKBUILD for my self, but actually it wont compile.
Here is what i wrote
pkgname=xfburn-svn
pkgver=23953
pkgrel=1
pkgdesc="Xfburn, burning program for XFCE4"
url="http://www.xfce.org/"
depends=('gtk2' 'shared-mime-info' 'hicolor-icon-theme' 'libexif'
'librsvg' 'pcre' 'fam' 'hal' 'eject'
'exo-svn' 'libxfce4util-svn')
makedepends=('subversion' 'intltool' 'xfce4-dev-tools')
_svntrunk=http://svn.xfce.org/svn/xfce/xfburn/trunk/
_svnmod=xfburn
build() {
msg "Updating SVN entries for $_svnmod ..."
cd $startdir/src
svn co $_svntrunk $_svnmod
cd $_svnmod
msg "Finished update, starting build ..."
./autogen.sh
make || return 1
make DESTDIR=$startdir/pkg install
}
but it fails at ./autogen. could anyone try this PKGBUILD and eventually fix it?
thx
Offline
Do you get any error message?
Offline
Check this PKGBUILD
pkgname=xfburn-svn
pkgver=23953
pkgrel=4
pkgdesc="Xfburn, burning program for XFCE4"
url="http://www.xfce.org/"
depends=('gtk2' 'shared-mime-info' 'hicolor-icon-theme' 'libexif'
'librsvg' 'pcre' 'fam' 'hal' 'eject'
'exo-svn' 'libxfce4util-svn' 'cdrtools' 'cdrdao')
makedepends=('subversion' 'intltool' 'xfce-devtools-svn' 'autoconf')
_svntrunk=http://svn.xfce.org/svn/xfce/xfburn/trunk/
_svnmod=xfburn
build() {
msg "Updating SVN entries for $_svnmod ..."
cd $startdir/src
svn co $_svntrunk $_svnmod
cd $_svnmod
msg "Finished update, starting build ..."
./autogen.sh --prefix=/opt/xfce4
make || return 1
make DESTDIR=$startdir/pkg install
}
Offline
Ahh, damn, i found the error forgot to enter a prefix with ./autogen.sh.
TY slubman!
Offline
It is the only missing package of XFCE... somebody (a developer) should put it into the repo...
Offline
Should not be in the repo since it's beta...
Offline
Should not be in the repo since it's beta...
So Gaim shouldn't be in the repo's either ?
Offline
Ideally not, but it seems people don't care running a beta version of Gaim. But I think if you ask the Gaim developers if the beta is suitable for production use (which I consider the current repo is...) they probably say no.
And because xfburn has not been tested a lot and there was only a 0.2.0beta release (which was not based on libburn, like trunk is atm.; so trunk is more like an alpha), I'd say it's not ready for current. Furthermore: developers are not very happy with bug reports of their product when it's from an experimental or in-development branch/trunk.
Offline
Furthermore: developers are not very happy with bug reports of their product when it's from an experimental or in-development branch/trunk.
In my experience most developers love it when you're reporting bugs of their experimental/in-development branch/trunk. Bugs get solved, new functionality gets added etc. while the main branch gets its obligatory (security) fixes.
Offline
Yeah sometimes they do, when trunk is more or less ready for a release (after an rc or beta) or reports from the group of testers who know where they're talking about, but when you're still working on the code and you get (upstream) reports from bug trackers like Ubuntu's launchpad, it can be quite annoying.
So your right when the reports are from users who can compile they own software and test your fixes, but not from people who say "The package is broken in the Arch repository and I can only type pacman -Syu". Nothing against those people, but they can not work because of trunk snapshots in stable repositories.
Offline