You are not logged in.

#1 2006-08-06 18:35:46

gs
Member
From: UK
Registered: 2004-03-06
Posts: 147

A Twinkle PKGBUILD

# $Id: PKGBUILD,v 1.13 2006/07/16 17:09:54 gs Exp $
# Maintainer: 

pkgname=twinkle
pkgver=0.8.1
pkgrel=1
pkgdesc="A SIP softphone for Qt"
arch=(i686 x86_64)
url="http://www.twinklephone.com/"
source=(http://www.xs4all.nl/~mfnboer/twinkle/download/twinkle-$pkgver.tar.gz)
#depends=('gtk2-perl' 'librsvg' 'perl-file-mimeinfo')
makedepends=('commoncpp2' 'ccrtp' 'qt' 'libsndfile' 'boost')
md5sums=('245ffd3b4a6f968d8f80d42f6aad079c')

build() {
  cd $startdir/src/twinkle-$pkgver
  ./configure --disable-qt-check --prefix=/usr
  make || return 1
  make DESTDIR=$startdir/pkg install
}

I have not yet separated the depends from the makedepends. Also I have not used the application, but it builds!

It is probably better to have --prefix=/opt/kde.

The thing is that I have not yet been able to find a voip/sip application that can build in arch64. So maybe this is a first?

Geoff


What the beep was that?

Offline

#2 2006-08-07 00:26:42

gs
Member
From: UK
Registered: 2004-03-06
Posts: 147

Re: A Twinkle PKGBUILD

This is more like a pukka makepkg. Observe the note about the sequence of installing dependencies, for the makepkg process. 'speex' may not strictly be a dependency.

The documentation is of very high standard. I have tested the installation and it shows every sign of working -- I have called myself succesfully!

# $Id: PKGBUILD, 2006/07/16 17:09:54 Geoff Slocock -- gslocock@yahoo.co.uk
# Maintainer: 
# NOTE: You have to install 'commoncpp2' before 'ccrtp', before running makepkg.
pkgname=twinkle
pkgver=0.8.1
pkgrel=1
pkgdesc="A SIP softphone for Qt"
arch=(i686 x86_64)
url="http://www.twinklephone.com/"
source=(http://www.xs4all.nl/~mfnboer/twinkle/download/twinkle-$pkgver.tar.gz)
depends=('speex' 'kdelibs' 'boost' 'ccrtp')
makedepends=('commoncpp2' 'qt' 'libsndfile')
md5sums=('245ffd3b4a6f968d8f80d42f6aad079c')

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

Geoff


What the beep was that?

Offline

#3 2006-08-07 01:08:02

gs
Member
From: UK
Registered: 2004-03-06
Posts: 147

Re: A Twinkle PKGBUILD

Actually, it will install and run without kdelibs. The manual says:

These features are only available when your system provides KDE libraries. Twinkle can also run on systems without KDE libraries, but you will lack these features.

    * Balloon popup from system tray when a call comes in
    * Interface to KAddressBook: dial phone numbers from your address book
    * Display names from KAddressBook on incoming calls (new)
    * Display photos from KAddressBook on incoming calls (new)

So, I guess there should be two PKGBUILDS. For gnome (and other non-kde systems) systems it would look like this:

# $Id: PKGBUILD, 2006/07/16 17:09:54 Geoff Slocock -- gslocock@yahoo.co.uk
# Maintainer:
# NOTE: You have to install 'commoncpp2' before 'ccrtp', before running makepkg.
pkgname=twinkle
pkgver=0.8.1
pkgrel=1
pkgdesc="A SIP softphone for Qt -- adaptation for non kde installations"
arch=(i686 x86_64)
url="http://www.twinklephone.com/"
source=(http://www.xs4all.nl/~mfnboer/twinkle/download/twinkle-$pkgver.tar.gz)
depends=('speex' 'boost' 'ccrtp')
makedepends=('commoncpp2' 'qt' 'libsndfile')
md5sums=('245ffd3b4a6f968d8f80d42f6aad079c')

build() {
  cd $startdir/src/twinkle-$pkgver
  ./configure --disable-qt-check --prefix=/usr
  make || return 1
  make DESTDIR=$startdir/pkg install
}

Geoff


What the beep was that?

Offline

#4 2006-08-07 04:46:21

AndyRTR
Developer
From: Magdeburg/Germany
Registered: 2005-10-07
Posts: 1,640

Re: A Twinkle PKGBUILD

gs wrote:

Actually, it will install and run without kdelibs. The manual says:

These features are only available when your system provides KDE libraries. Twinkle can also run on systems without KDE libraries, but you will lack these features.

    * Balloon popup from system tray when a call comes in
    * Interface to KAddressBook: dial phone numbers from your address book
    * Display names from KAddressBook on incoming calls (new)
    * Display photos from KAddressBook on incoming calls (new)

So, I guess there should be two PKGBUILDS. For gnome (and other non-kde systems) systems...

for additional depends you can leave a comment in a foo.install script.

Anyway this is not the right section for usual  PKGBUILD discussion. AUR req. or Make pkg are better places.

Offline

#5 2006-08-07 07:24:22

gs
Member
From: UK
Registered: 2004-03-06
Posts: 147

Re: A Twinkle PKGBUILD

I think the issue is a bit more subtle than that.

At the makepkg stage -- whether or not kdelibs is specified as a 'depends' -- ./configure searches to see if kdelibs is present. and this is the way that the binary gets pre-shaped.

Thus, for example, a pkg.tar.gz built on a kde system will most probably fail when installed on a non-kde system. Similarly, a non-kde built binary will produce a feature reduced version when installed on a kde machine.

Thus, as far as I can see, this a genuinely forked build. I think this is not really generalisable enough to be an issue in the other fora.

Geoff


What the beep was that?

Offline

#6 2006-08-07 07:57:30

kth5
Member
Registered: 2004-04-29
Posts: 655
Website

Re: A Twinkle PKGBUILD

I have twinkle in ArchPPC for some time now, any interest there that I should add it to extra on i686 as well?

I guess the kde stuff is being linked on buildtime, not runtime. So it's probably not as simple as to add a message to the install script that tells users to install kdelibs if they wanted to have some features.


I recognize that while theory and practice are, in theory, the same, they are, in practice, different. -Mark Mitchell

Offline

#7 2006-08-07 07:57:43

gs
Member
From: UK
Registered: 2004-03-06
Posts: 147

Re: A Twinkle PKGBUILD

I agree, though, that a install script could produce a comment saying that, if 'speex' and/or 'ilibc' is installed, extra functionality will be obtained -- as per the documentation at http://www.twinklephone.com/.

Geoff


What the beep was that?

Offline

#8 2006-08-07 08:10:33

gs
Member
From: UK
Registered: 2004-03-06
Posts: 147

Re: A Twinkle PKGBUILD

kth5 said:

I have twinkle in ArchPPC for some time now, any interest there that I should add it to extra on i686 as well?

This seems to be the only functional arch64 sip/voip, so there must be a demand.

Do you think the two builds should be:

1) twinkle-for-kde
pkgdesc="A SIP softphone for Qt for installation on kde systems"

2) twinkle-without-kde
pkgdesc="A SIP softphone for Qt for installation on non-kde systems"

It may also be that a kde build will gracefully fail and not provide the kdelibs features, when installed on a non-kde system. In that case --prefix=/usr could be better.

Geoff


What the beep was that?

Offline

#9 2006-08-07 08:16:44

kth5
Member
Registered: 2004-04-29
Posts: 655
Website

Re: A Twinkle PKGBUILD

yes, i believe two seperate pkgbuilds to be better. but make it twinkle and twinke-kdefree. this would synchronize nicely with amarok. smile


I recognize that while theory and practice are, in theory, the same, they are, in practice, different. -Mark Mitchell

Offline

#10 2006-08-07 08:24:00

gs
Member
From: UK
Registered: 2004-03-06
Posts: 147

Re: A Twinkle PKGBUILD

cool!


What the beep was that?

Offline

#11 2006-08-07 08:34:26

AndyRTR
Developer
From: Magdeburg/Germany
Registered: 2005-10-07
Posts: 1,640

Re: A Twinkle PKGBUILD

gs wrote:

This seems to be the only functional arch64 sip/voip, so there must be a demand.

I'd rather like to see Ekiga back working  :?

Offline

#12 2006-08-07 16:01:50

kth5
Member
Registered: 2004-04-29
Posts: 655
Website

Re: A Twinkle PKGBUILD

Just made the PKGBUILDs for PPC:

Twinkle:
http://cvs.archlinuxppc.org/viewcvs/net … root=extra

Twinkle (w/o KDE):
http://cvs.archlinuxppc.org/viewcvs/net … root=extra

Have fun with those! smile

PS: The plan is that I add them to extra tonight.


I recognize that while theory and practice are, in theory, the same, they are, in practice, different. -Mark Mitchell

Offline

#13 2006-08-07 18:09:09

gs
Member
From: UK
Registered: 2004-03-06
Posts: 147

Re: A Twinkle PKGBUILD

I have had a look at both links. Unless I am doing something wrong, both PKGBUILDS are of the kdefree version.

Geoff


What the beep was that?

Offline

#14 2006-08-07 19:09:20

gs
Member
From: UK
Registered: 2004-03-06
Posts: 147

Re: A Twinkle PKGBUILD

I have had another look. It checks out OK.


What the beep was that?

Offline

#15 2006-08-08 21:07:27

gs
Member
From: UK
Registered: 2004-03-06
Posts: 147

Re: A Twinkle PKGBUILD

It's all fine. I have built it with your PKGBUILD. I have noticed this in the app news page, though.

09 jul 2006 - Release 0.8.1
===========================
- Removed iLBC source code from Twinkle. To use iLBC you can
  link Twinkle with the ilbc library (ilbc package). When you
  have the ilbc library installed on your system, then Twinkle's
  configure script will automatically setup the Makefiles to
  link with the library.

When I built, I had ilbc installed; so I have the enhanced binary. So a msg to the user about that option of linking might be a useful extra. ilbc, however, is not yet packaged.

So, the other option is to package it and make it a dependency.

HTH

Geoff

BTW: A very nice app. The roadmap is for all the facilities to be incorporated, so it may become a true ekiga alternative


What the beep was that?

Offline

Board footer

Powered by FluxBB