Package Details: zoiper 3.3-2

Git Clone URL: https://aur.archlinux.org/zoiper.git (read-only)
Package Base: zoiper
Description: An IAX and SIP VoIP softphone
Upstream URL: http://www.zoiper.com/
Licenses: custom
Submitter: ava1ar
Maintainer: Xavion
Last Packager: Xavion
Votes: 48
Popularity: 0.200620
First Submitted: 2009-10-15 10:31
Last Updated: 2017-01-10 23:13

Latest Comments

Xavion commented on 2017-01-25 06:18

Adding a comment like that to the PKGBUILD shouldn't be necessary. Also, not everyone uses 'pacaur': I, for one, have stayed with 'yaourt'.

ohmysql commented on 2017-01-25 05:47

Suggestion:

adding a comment that says 1) Do NOT mark the package out of date if you need to manually download Zoiper. 2) The default configuration for pacaur as of 2017-01-25 is to put it in ~/.cache/pacaur/zoiper

Moving the downloaded file there should work. However do NOT mark this package out of date or otherwise bother me to figure out where your PKGBUILD directory is.

etc.

Xavion commented on 2017-01-10 23:15

Yes, none of that stuff should be necessary anymore. I have amended the PKGBUILD. Thanks for bringing this to my attention.

ilmagno commented on 2017-01-10 02:48

The tarball now has a x86_64 version, can this be updated so that it doesn't require the 32bit libraries on a x86_64 system?

Xavion commented on 2015-11-13 20:25

View the PKGBUILD and you'll see that "lib32-pangox-compat" is already listed in the "depends" array for "x86_64" systems.

fdservices commented on 2015-11-13 16:38

Another dependency: lib32-pangox-compat

Xavion commented on 2015-06-11 20:30

Did you actually read that message before pasting it here and flagging the package out-of-date?

Manually download the tarball into the directory containing the PKGBUILD, then rebuild the package.

darkdirk commented on 2015-06-11 16:57

Fails with: "WARNING: There is no longer a direct download link for the Zoiper tarball. Get it manually from: http://www.zoiper.com/en/voip-softphone/download/zoiper3/for/linux"

balage commented on 2015-02-19 11:48

Okay, I accept it.

Xavion commented on 2015-02-18 19:47

The location of "${startdir}" depends on a number of factors. Teaching people how to find it is beyond the scope of any single PKGBUILD.

Anyway, I feel that "${startdir}" infers the directory containing the PKGBUILD. Also, most confused newbies would simply Google "PKGBUILD startdir".

All comments