You are not logged in.

#1 2008-04-14 10:50:12

faelar
Member
From: Amiens (FR)
Registered: 2007-12-18
Posts: 232
Website

mumbles PKGBUILD

pkgname=mumbles
pkgver=0.4_1
pkgrel=1
pkgdesc="A plugin driven, modern notification system for Gnome"
url="http://www.mumbles-project.org/"
license=('GPL')
arch=('i686' 'x86_64')
depends=('python>=2.4' 'pygtk' 'pycairo' 'dbus-python' 'setuptools')
makedepends=('')
source=(http://downloads.sourceforge.net/mumbles/$pkgname_0.4-1.tar.gz)
md5sums=('a6b24223dc23e5022332586ffc454e84')

build() {
}

It's my first PKGBUILD but I'm not able to understand what I must do to put the files in the right place.

And I'm no sure about the  " - " > " _ " conversion. Is there a possibility to use $pkgver in the download location for exemple ?

Thank you for the help smile

Offline

#2 2008-04-14 10:57:32

brebs
Member
Registered: 2007-04-03
Posts: 3,742

Re: mumbles PKGBUILD

Yes. Might need to wrap it in curly brackets, i.e.:  ${pkgver}

Offline

#3 2008-04-14 12:44:09

Stefan Husmann
Member
From: Germany
Registered: 2007-08-07
Posts: 1,391

Re: mumbles PKGBUILD

No, the version number originally is 0.4-1, contains a hyphen and so cannot be used in $pkgver. You can define another variable _pkgver=0.4-1 (with an underscore) and use that in the source array. This is not exactly allowed by the packaging standards, but a widespread compromise.

Curly braces may be needed sometimes when the variable's name starts with an underscore.

Offline

#4 2008-04-14 12:55:33

brebs
Member
Registered: 2007-04-03
Posts: 3,742

Re: mumbles PKGBUILD

Ah, didn't notice the _ vs - smile

Defining and using $_pkgver is not recommended for packages in the AUR, because the AUR file list cannot replace it with its value.

Offline

#5 2008-04-14 13:31:26

Stefan Husmann
Member
From: Germany
Registered: 2007-08-07
Posts: 1,391

Re: mumbles PKGBUILD

Well, I wanted to suggest to define

pkgver=0.4_1
_pkgver=0.4-1

and to use pkgver for AUR and _pkgver for other issues within the PKGBUILD. This should work, but strongly spoken no user-defined variables are allowed at all.

Offline

#6 2008-04-14 16:08:42

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,839

Re: mumbles PKGBUILD

Re putting files in the right places - man PKGBUILD and various wiki pages have the details. Generally best to read them before you start. wink

Offline

#7 2008-04-14 21:48:22

faelar
Member
From: Amiens (FR)
Registered: 2007-12-18
Posts: 232
Website

Re: mumbles PKGBUILD

In fact you don't need to compile anything because it's a python script. I can launch it directly after extracting the tar.gz
You have differents plugins (pidgin, firefox etc...) you must copy in ~/.mumbles/plugins
I forgot to tell that I'm not familiar enought with linux folders :s
So my question is "where python scripts are supposed to be put ?"

Re putting files in the right places - man PKGBUILD and various wiki pages have the details. Generally best to read them before you start.

That's what I did, but I don't fully understand the PKGBUILD writing process. I'm sorry if my questions are trivials,
Else barkets work well thank you for the suggestion smile

Offline

#8 2008-04-15 11:17:17

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,839

Re: mumbles PKGBUILD

Have a look at some python PKGBUILDS in our CVS and/or the AUR for some examples of how it's done.

Offline

#9 2008-04-15 17:41:05

faelar
Member
From: Amiens (FR)
Registered: 2007-12-18
Posts: 232
Website

Re: mumbles PKGBUILD

pkgname=mumbles
pkgver=0.4_1
pkgrel=1
pkgdesc="A plugin driven, modern notification system for Gnome"
url="http://www.mumbles-project.org/"
license=('GPL')
arch=('i686' 'x86_64')
depends=('python>=2.4' 'pygtk' 'pycairo' 'dbus-python' 'setuptools')
makedepends=('')
source=(http://downloads.sourceforge.net/mumbles/${pkgname}_0.4-1.tar.gz)
md5sums=('a6b24223dc23e5022332586ffc454e84')

build() {
    cd $startdir/src/$pkgname-0.4
    python setup.py install --root=$startdir/pkg/
}

Installation was fine, but after that, trying to launch mumbles returns me an error about MumblesGlobals which can't be imported. The file is located in /usr/lib/python2.5/site-packages/src/
I opened the mumble file in /usr/bin/ :

#!/usr/bin/python
#
# THIS FILE IS PART OF THE MUMBLES PROJECT AND IS LICENSED UNDER THE GPL.
# SEE THE 'COPYING' FILE FOR DETAILS
#
# Mumbles Launcher Script
#
#------------------------------------------------------------------------
import os, sys

sys.path.append("/usr/share/python-support/mumbles/src/")
os.environ.setdefault("MUMBLES_PATH", "/usr/share/mumbles/")

from MumblesGlobals import *
from Mumbles import *

mumbles = Mumbles()
sys.exit(mumbles.main())

How can I fix this issue ?

Offline

#10 2008-12-23 15:55:09

Mr Green
Forum Fellow
From: U.K.
Registered: 2003-12-21
Posts: 5,899
Website

Re: mumbles PKGBUILD

Did you ever get mumbles working? using pkgbuild in AUR have to tweak it to build, but getting errors when running it


Mr Green

Offline

#11 2009-02-09 01:16:40

merdenoms
Member
Registered: 2008-12-02
Posts: 6
Website

Re: mumbles PKGBUILD

mumbles PKGBUILD in AUR is troublesome...can't build it..can someone handle it?

Offline

#12 2009-02-09 07:32:33

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,839

Re: mumbles PKGBUILD

Closing this thread, as it dates back to last April 2008.

merdenoms - I would suggest you start a new thread about your build issue, with details of the actual problem. Posting "can't build it" is pointless.

Also worth noting - there hasn't been a mumbles release since August 2007, and the mumbles package in the AUR is currently orphaned.

Offline

Board footer

Powered by FluxBB