These ebuild pull from Digium's CVS for Asterisk. This is the primary means that a majority of Asterisk users use to keep Asterisk up-to-date. I realized that 1.0 is about to be released but some will still continue to use CVS. There is a previous bug opened for this, but it has been ignored for quite some time. Reproducible: Always Steps to Reproduce:
Created attachment 36203 [details] asterisk-cvs-0.6.ebuild Version 0.6 of the asterisk-cvs ebuild.
Created attachment 36204 [details] asterisk.rc6 asterisk-cvs initscript to go in net-misc/asterisk-cvs/files
Created attachment 36205 [details] zaptel-cvs-0.8.ebuild Version 0.8 of the Zaptel-CVS ebuild
Created attachment 36206 [details] zaptel-cvs-modulesd.patch Zaptel patch to go in net-misc/zaptel-cvs/files
Created attachment 36207 [details] libpri-cvs-0.1.ebuild Version 0.1 of the libpri ebuild.
This ebuild works perfectly. The asterisk-cvs ebuild will use libpri or zaptel based on use flags. It also has a "docs" and "samples" use flags for documentation and sample configs.
see also bug #33345.
Yes, I know. I updated these ebuilds and that bug hasn't been looked at in the over 6 months it's been up.
After I got the files in the correct places both zaptel-cvs and asterisk-cvs installed without a hitch. libpri-cvs had a sandbox access violation but I don't belive I need it anyway. Thanks for the cvs ebuild. *CLI> show version Asterisk CVS-HEAD-07/31/04-22:25:26 built by root@moria.urgo.org on a i686 running Linux # ACCEPT_KEYWORDS="~x86" emerge libpri-cvs Calculating dependencies ...done! >>> emerge (1 of 1) net-libs/libpri-cvs-0.1 to / >>> Unpacking source... * Fetching CVS module libpri into /usr/portage/distfiles/cvs-src/libpri-cvs... * Running cvs -q -f -z4 -d ":pserver:anoncvs:anoncvs@cvs.digium.com:/usr/cvsroot" login Logging in to :pserver:anoncvs@cvs.digium.com:2401/usr/cvsroot * Running cvs -q -f -z4 -d ":pserver:anoncvs@cvs.digium.com:/usr/cvsroot" update -dP libpri * Copying libpri from /usr/portage/distfiles/cvs-src/libpri-cvs... * CVS module libpri is now in /var/tmp/portage/libpri-cvs-0.1/work >>> Source unpacked. Makefile:83: .depend: No such file or directory ./mkdep -Wall -Werror -Wstrict-prototypes -Wmissing-prototypes -g `ls *.c` gcc -Wall -Werror -Wstrict-prototypes -Wmissing-prototypes -g -c -o pri.o pri.c gcc -Wall -Werror -Wstrict-prototypes -Wmissing-prototypes -g -c -o q921.o q921.c gcc -Wall -Werror -Wstrict-prototypes -Wmissing-prototypes -g -c -o prisched.o prisched.c gcc -Wall -Werror -Wstrict-prototypes -Wmissing-prototypes -g -c -o q931.o q931.c ar rcs libpri.a pri.o q921.o prisched.o q931.o ranlib libpri.a gcc -fPIC -Wall -Werror -Wstrict-prototypes -Wmissing-prototypes -g -o pri.lo -c pri.c gcc -fPIC -Wall -Werror -Wstrict-prototypes -Wmissing-prototypes -g -o q921.lo -c q921.c gcc -fPIC -Wall -Werror -Wstrict-prototypes -Wmissing-prototypes -g -o prisched.lo -c prisched.c gcc -fPIC -Wall -Werror -Wstrict-prototypes -Wmissing-prototypes -g -o q931.lo -c q931.c gcc -shared -Wl,-soname,libpri.so.1 -o libpri.so.1.0 pri.lo q921.lo prisched.lo q931.lo /sbin/ldconfig -n . ln -sf libpri.so.1 libpri.so make: Nothing to be done for `all'. >>> Install libpri-cvs-0.1 into /var/tmp/portage/libpri-cvs-0.1/image/ category net-libs mkdir -p /usr/lib mkdir -p /usr/include install -m 644 libpri.h /usr/include ACCESS DENIED open_wr: /usr/include/libpri.h install: cannot create regular file `/usr/include/libpri.h': Permission denied make: *** [install] Error 1 !!! ERROR: net-libs/libpri-cvs-0.1 failed. !!! Function src_install, Line 32, Exitcode 2 !!! make install failed --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-net-libs_-_libpri-cvs-0.1-2953.log" open_wr: /usr/include/libpri.h --------------------------------------------------------------------------------
There is a typo in asterisk-cvs-0.6.ebuild : the IUSE flag used for the documentation is "doc" as usually seen in ebuilds, but anywhere else in this ebuild it appears as "docs". It is advisable to use "doc" anywhere.
The problem with libpri-cvs is in the make install line It should be: make INSTALL_PREFIX=${D} ARCH=${MY_ARCH} install || die "make install failed"
Asterisk 1.0 will be released / presented at Astricon. Will the ebuild be replaced by an ebuild for 1.0 then? (RC2 was already released about 2 weeks ago).
as Remco Barendse announced, 1.0 was released today and if you use the cvs ebuilds today you'll get version 1.0. *CLI> show version Asterisk CVS-HEAD-09/23/04-13:20:08 ftp://ftp.asterisk.org/pub/telephony/asterisk/ File: asterisk-1.0.0.tar.gz 9332 KB 9/23/2004 8:06:00 AM
Asterisk 1.00 stable is now in portage but zaptel is still at version 0.9.1 therefore Asterisk will not emerge. Is this because I did emerge sync just a couple of minutes too soon or is zaptel lagging behind?
Asterisk 1.0.1 is now available.
Created attachment 41682 [details] modulesd patch failed When trying to emerge the zaptel-cvs ebuild I had an error that seems to relate to the modulesd patch I installed. Could it be that the CVS version of whatever is being patched has moved on somewhat and that has now broken the patch?
Asterisk-cvs build does not seem to recognise the nozaptel use-flag.
I'm guessing you know these ebuilds are not going to happen. These packages are not stable enough for cvs ebuilds.
