edenyard
New member
The way I've built GO for my Arch Linux system is to use the PKGBUILD found in the Arch AUR. That builds successfully and gives me a working GO but I notice that the version is 0.3.0.6.1114.
This is the content of the PKGBUILD file:
Hunting around the Sourceforge site, I clicked on this link:
I notice that the version of source code found under (for example) Debian-6.0 is grandorgue_0.3.1.1159.orig.tar.gz
I don't know much about the different methods of building packages from source, but I was wondering why the version I'm getting seems to be quite a few versions behind what appears to be available for other Linux distros - 0.3.0.6.1114 compared with 0.3.1.1159.
So - some questions:
1. Would I be better off running a newer version of GO?
2. If (1) is 'yes', how do I modify the Arch PKGBUILD file to get a newer version? I can't see anything in the PKGBUILD that specifically determines what version is downloaded and built.
3. Will building a newer version give me the reverb feature that I notices is being discussed in another thread?
Thanks for any guidance or clues on this matter. As I said, I know very little about this side of the business, so please don't anybody be afraid to point out basic things that are blindingly obvious to the more knowledgeable folk on this forum!
Cheers,
Gerald.
This is the content of the PKGBUILD file:
Code:
[COLOR=#000000]# Maintainer: Piotr Porada <[email protected]>
pkgname=grandorgue-svn
pkgver=1114
pkgrel=1
pkgdesc="A free pipe organ sampler compatible with Hauptwerk v1 samples"
arch=('i686' 'x86_64')
url="http://ourorgan.sf.net"
license=('GPL')
groups=('multimedia')
depends=('wxgtk' 'jack')
makedepends=('cmake' 'subversion' 'wxgtk' 'jack')
provides=('grandorgue')
conflicts=('grandorgue')
replaces=()
backup=()
options=()
install=
source=()
noextract=()
md5sums=() #generate with 'makepkg -g'
_svntrunk="https://ourorgan.svn.sourceforge.net/svnroot/ourorgan/trunk"
_svnmod="trunk"
build() {
cd "$srcdir"
msg "Connecting to SVN server...."
if [[ -d "$_svnmod/.svn" ]]; then
(cd "$_svnmod" && svn up -r "$pkgver")
else
svn co "$_svntrunk" --config-dir ./ "$_svnmod"
fi
msg "SVN checkout done or server timeout"
msg "Starting build..."
rm -rf "$srcdir/$_svnmod-build"
mkdir "$srcdir/$_svnmod-build"
cd "$srcdir/$_svnmod-build"
#
# BUILD HERE
#
### cmake -DUNICODE=1 -DCMAKE_BUILD_TYPE=Release -G "Unix Makefiles" "$srcdir/$_svnmod"
cmake -DUNICODE=1 -DCMAKE_BUILD_TYPE=Release -DDOCBOOK_DIR=/usr/share/xml/docbook/xsl-stylesheets -G "Unix Makefiles" "$srcdir/$_svnmod"
}
package() {
cd "$srcdir/$_svnmod-build"
make DESTDIR="$pkgdir/" install
}
# vim:set ts=2 sw=2 et:
[/COLOR]
Hunting around the Sourceforge site, I clicked on this link:
Code:
[COLOR=#000000]Direct link to the repositories: [/COLOR][URL="http://download.opensuse.org/repositories/home:/e9925248:/grandorgue/"][COLOR=#000000]http://download.opensuse.org/repositories/home:/e9925248:/grandorgue/[/COLOR][/URL]
I notice that the version of source code found under (for example) Debian-6.0 is grandorgue_0.3.1.1159.orig.tar.gz
I don't know much about the different methods of building packages from source, but I was wondering why the version I'm getting seems to be quite a few versions behind what appears to be available for other Linux distros - 0.3.0.6.1114 compared with 0.3.1.1159.
So - some questions:
1. Would I be better off running a newer version of GO?
2. If (1) is 'yes', how do I modify the Arch PKGBUILD file to get a newer version? I can't see anything in the PKGBUILD that specifically determines what version is downloaded and built.
3. Will building a newer version give me the reverb feature that I notices is being discussed in another thread?
Thanks for any guidance or clues on this matter. As I said, I know very little about this side of the business, so please don't anybody be afraid to point out basic things that are blindingly obvious to the more knowledgeable folk on this forum!
Cheers,
Gerald.