Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: atrpms: devel

Updates for Asterisk and co

  

 
atrpms devel RSS feed   Index | Next | Previous | View Threaded


tim.verhoeven.be at gmail

Dec 14, 2007, 6:07 AM

Post #1 of 18 (5276 views)
Permalink
Updates for Asterisk and co
Hi,

I'm building a new Asterisk system here (on CentOS 5) and since atrpms
seemed to be the only one who had decent build and recent packages
I've used those to start the install.

In the course of the install I've made some changes and added a couple
of new packages. And I would like to contribute them back to atrpms.
What is the best way to go about this ?

What I have done :

- Created misdn and misdnuser packages (www.misdn.org). misdn is a
better ISDN implementation then the bristuff one (and simpler to
integrate into asterisk)
- Added a asterisk-misdn package with the asterisk module for misdn.
- Created agx-ast-addons package. This is a set of asterisk modules
there were in asterisk but because of license issues are now
maintained seperate. (I needed the fax stuff from it).

I'm ofcourse willing to keep this stuff maintained.

Regards,
Tim

--
Tim Verhoeven - tim.verhoeven.be [at] gmail - 0479 / 88 11 83

Hoping the problem magically goes away by ignoring it is the
"microsoft approach to programming" and should never be allowed.
(Linus Torvalds)

_______________________________________________
atrpms-devel mailing list
atrpms-devel [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-devel


Axel.Thimm at ATrpms

Dec 14, 2007, 8:17 AM

Post #2 of 18 (5131 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
Hi,

On Fri, Dec 14, 2007 at 03:07:18PM +0100, Tim Verhoeven wrote:
> Hi,
>
> I'm building a new Asterisk system here (on CentOS 5) and since atrpms
> seemed to be the only one who had decent build and recent packages
> I've used those to start the install.
>
> In the course of the install I've made some changes and added a couple
> of new packages. And I would like to contribute them back to atrpms.

Thanks!

> What is the best way to go about this ?

Send me a ssh public key in PM. :)

> What I have done :
>
> - Created misdn and misdnuser packages (www.misdn.org). misdn is a
> better ISDN implementation then the bristuff one (and simpler to
> integrate into asterisk)
> - Added a asterisk-misdn package with the asterisk module for misdn.
> - Created agx-ast-addons package. This is a set of asterisk modules
> there were in asterisk but because of license issues are now
> maintained seperate. (I needed the fax stuff from it).
>
> I'm ofcourse willing to keep this stuff maintained.

Thanks^2 :)
--
Axel.Thimm at ATrpms.net


ptiggerdine at iinet

Dec 19, 2007, 7:53 PM

Post #3 of 18 (5124 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
Axel,

I've done some work on this in the past... I remember having problems
with the compile of misdn for the kernel. Also the testing of misdn is
still flaky...

Happy also to help.

Regards,

Peter Tiggerdine

Axel Thimm wrote:
> Hi,
>
> On Fri, Dec 14, 2007 at 03:07:18PM +0100, Tim Verhoeven wrote:
>
>> Hi,
>>
>> I'm building a new Asterisk system here (on CentOS 5) and since atrpms
>> seemed to be the only one who had decent build and recent packages
>> I've used those to start the install.
>>
>> In the course of the install I've made some changes and added a couple
>> of new packages. And I would like to contribute them back to atrpms.
>>
>
> Thanks!
>
>
>> What is the best way to go about this ?
>>
>
> Send me a ssh public key in PM. :)
>
>
>> What I have done :
>>
>> - Created misdn and misdnuser packages (www.misdn.org). misdn is a
>> better ISDN implementation then the bristuff one (and simpler to
>> integrate into asterisk)
>> - Added a asterisk-misdn package with the asterisk module for misdn.
>> - Created agx-ast-addons package. This is a set of asterisk modules
>> there were in asterisk but because of license issues are now
>> maintained seperate. (I needed the fax stuff from it).
>>
>> I'm ofcourse willing to keep this stuff maintained.
>>
>
> Thanks^2 :)
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> atrpms-devel mailing list
> atrpms-devel [at] atrpms
> http://lists.atrpms.net/mailman/listinfo/atrpms-devel

_______________________________________________
atrpms-devel mailing list
atrpms-devel [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-devel


Axel.Thimm at ATrpms

Dec 26, 2007, 1:56 AM

Post #4 of 18 (5134 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
Hi,

On Thu, Dec 20, 2007 at 01:53:07PM +1000, Peter Tiggerdine wrote:
> Axel Thimm wrote:
> > On Fri, Dec 14, 2007 at 03:07:18PM +0100, Tim Verhoeven wrote:
> >> I'm building a new Asterisk system here (on CentOS 5) and since
> >> atrpms seemed to be the only one who had decent build and recent
> >> packages I've used those to start the install.
> >>
> >> In the course of the install I've made some changes and added a
> >> couple of new packages. And I would like to contribute them back
> >> to atrpms.
> >
> > Thanks!
> >
> >> What is the best way to go about this ?
> >
> > Send me a ssh public key in PM. :)

Tim's packages are under http://people.atrpms.net/~tverhoeven/

I already imported the misdn(user) and asterisk packages, but I have
some problems with agx-ast-addons:

| -- Check for working CXX compiler: /usr/bin/c++ -- works
| CMake Error: MISSING HEADER: glibconfig.h
| -- Configuring done

I already added glib2-devel as a BR, but that didn't help.

> >> What I have done :
> >>
> >> - Created misdn and misdnuser packages (www.misdn.org). misdn is a
> >> better ISDN implementation then the bristuff one (and simpler to
> >> integrate into asterisk)
> >> - Added a asterisk-misdn package with the asterisk module for misdn.
> >> - Created agx-ast-addons package. This is a set of asterisk modules
> >> there were in asterisk but because of license issues are now
> >> maintained seperate. (I needed the fax stuff from it).
> >>
> >> I'm ofcourse willing to keep this stuff maintained.
> >
> > Thanks^2 :)

Thanks again! :)

> Axel,
>
> I've done some work on this in the past... I remember having problems
> with the compile of misdn for the kernel. Also the testing of misdn is
> still flaky...
>
> Happy also to help.
>
> Regards,
>
> Peter Tiggerdine

That would be great, could you give the new packages some testing?
--
Axel.Thimm at ATrpms.net


tim.verhoeven.be at gmail

Dec 26, 2007, 2:15 AM

Post #5 of 18 (5119 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
On Dec 26, 2007 10:56 AM, Axel Thimm <Axel.Thimm [at] atrpms> wrote:
>
> Tim's packages are under http://people.atrpms.net/~tverhoeven/
>
> I already imported the misdn(user) and asterisk packages, but I have
> some problems with agx-ast-addons:
>
> | -- Check for working CXX compiler: /usr/bin/c++ -- works
> | CMake Error: MISSING HEADER: glibconfig.h
> | -- Configuring done
>
> I already added glib2-devel as a BR, but that didn't help.

I will see what that could be.

Regards,
Tim

--
Tim Verhoeven - tim.verhoeven.be [at] gmail - 0479 / 88 11 83

Hoping the problem magically goes away by ignoring it is the
"microsoft approach to programming" and should never be allowed.
(Linus Torvalds)

_______________________________________________
atrpms-devel mailing list
atrpms-devel [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-devel


tim.verhoeven.be at gmail

Mar 13, 2008, 10:24 AM

Post #6 of 18 (4853 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
On Wed, Dec 26, 2007 at 10:56 AM, Axel Thimm <Axel.Thimm [at] atrpms> wrote:
...snip...
>
> I already imported the misdn(user) and asterisk packages, but I have
> some problems with agx-ast-addons:
>
> | -- Check for working CXX compiler: /usr/bin/c++ -- works
> | CMake Error: MISSING HEADER: glibconfig.h
> | -- Configuring done
>
> I already added glib2-devel as a BR, but that didn't help.

I've tried to replicate that here, but I couldn't.. I first build a
newer version of the addons :

http://people.atrpms.net/~tverhoeven/agx-ast-addons-1.4.5-0.el5.src.rpm

And then I removed both glib2-devel as glib-devel from my system and
it would still compile. So could you try the new version and see if
that one also has it ?

In the mean time I've put the server in production with the asterisk,
asterisk-misdn, misdn and misdnuser packages from atrpms. And all
seems to be working fine.

I've seen you made some changes to the asterisk package. You added the
app_rxfax and app_txfax modules to it ? I've checked the code for
those in the src.rpm. But they are older version then the code in the
addons. So if we can get the addons to build could those modules be
removed again from the asterisk package ?

Regards,
Tim

--
Tim Verhoeven - tim.verhoeven.be [at] gmail - 0479 / 88 11 83

Hoping the problem magically goes away by ignoring it is the
"microsoft approach to programming" and should never be allowed.
(Linus Torvalds)

_______________________________________________
atrpms-devel mailing list
atrpms-devel [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-devel


Axel.Thimm at ATrpms

Mar 20, 2008, 5:35 AM

Post #7 of 18 (4840 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
On Thu, Mar 13, 2008 at 06:24:53PM +0100, Tim Verhoeven wrote:
> On Wed, Dec 26, 2007 at 10:56 AM, Axel Thimm <Axel.Thimm [at] atrpms> wrote:
> ...snip...
> >
> > I already imported the misdn(user) and asterisk packages, but I have
> > some problems with agx-ast-addons:
> >
> > | -- Check for working CXX compiler: /usr/bin/c++ -- works
> > | CMake Error: MISSING HEADER: glibconfig.h
> > | -- Configuring done
> >
> > I already added glib2-devel as a BR, but that didn't help.
>
> I've tried to replicate that here, but I couldn't.. I first build a
> newer version of the addons :
>
> http://people.atrpms.net/~tverhoeven/agx-ast-addons-1.4.5-0.el5.src.rpm
>
> And then I removed both glib2-devel as glib-devel from my system and
> it would still compile. So could you try the new version and see if
> that one also has it ?

I tried and it fails with

+ make
Scanning dependencies of target app_devstate
[ 12%] Building C object CMakeFiles/app_devstate.dir/app_devstate.o
Linking C shared module dist/app_devstate.so
[ 12%] Built target app_devstate
Scanning dependencies of target app_nv_backgrounddetect
[ 25%] Building C object CMakeFiles/app_nv_backgrounddetect.dir/app_nv_backgrounddetect.o
Linking C shared module dist/app_nv_backgrounddetect.so
[ 25%] Built target app_nv_backgrounddetect
Scanning dependencies of target app_nv_faxdetect
[ 37%] Building C object CMakeFiles/app_nv_faxdetect.dir/app_nv_faxdetect.o
Linking C shared module dist/app_nv_faxdetect.so
[ 37%] Built target app_nv_faxdetect
Scanning dependencies of target app_pickup2
[ 50%] Building C object CMakeFiles/app_pickup2.dir/app_pickup2.o
Linking C shared module dist/app_pickup2.so
[ 50%] Built target app_pickup2
Scanning dependencies of target app_rxfax
[ 62%] Building C object CMakeFiles/app_rxfax.dir/app_rxfax.o
/builddir/agx-ast-addons/app_rxfax.c:27:20: error: tiffio.h: No such file or directory
In file included from /usr/include/spandsp.h:91,
from /builddir/agx-ast-addons/app_rxfax.c:29:
/usr/include/spandsp/t4.h:217: error: expected specifier-qualifier-list before 'TIFF'


> In the mean time I've put the server in production with the asterisk,
> asterisk-misdn, misdn and misdnuser packages from atrpms. And all
> seems to be working fine.
>
> I've seen you made some changes to the asterisk package. You added the
> app_rxfax and app_txfax modules to it ? I've checked the code for
> those in the src.rpm. But they are older version then the code in the
> addons. So if we can get the addons to build could those modules be
> removed again from the asterisk package ?
>
> Regards,
> Tim
>

--
Axel.Thimm at ATrpms.net


tim.verhoeven.be at gmail

Mar 21, 2008, 10:15 AM

Post #8 of 18 (4832 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
On Thu, Mar 20, 2008 at 1:35 PM, Axel Thimm <Axel.Thimm [at] atrpms> wrote:
>
> I tried and it fails with
>
> + make
> Scanning dependencies of target app_devstate
> [ 12%] Building C object CMakeFiles/app_devstate.dir/app_devstate.o
> Linking C shared module dist/app_devstate.so
> [ 12%] Built target app_devstate
> Scanning dependencies of target app_nv_backgrounddetect
> [ 25%] Building C object CMakeFiles/app_nv_backgrounddetect.dir/app_nv_backgrounddetect.o
> Linking C shared module dist/app_nv_backgrounddetect.so
> [ 25%] Built target app_nv_backgrounddetect
> Scanning dependencies of target app_nv_faxdetect
> [ 37%] Building C object CMakeFiles/app_nv_faxdetect.dir/app_nv_faxdetect.o
> Linking C shared module dist/app_nv_faxdetect.so
> [ 37%] Built target app_nv_faxdetect
> Scanning dependencies of target app_pickup2
> [ 50%] Building C object CMakeFiles/app_pickup2.dir/app_pickup2.o
> Linking C shared module dist/app_pickup2.so
> [ 50%] Built target app_pickup2
> Scanning dependencies of target app_rxfax
> [ 62%] Building C object CMakeFiles/app_rxfax.dir/app_rxfax.o
> /builddir/agx-ast-addons/app_rxfax.c:27:20: error: tiffio.h: No such file or directory
> In file included from /usr/include/spandsp.h:91,
> from /builddir/agx-ast-addons/app_rxfax.c:29:
> /usr/include/spandsp/t4.h:217: error: expected specifier-qualifier-list before 'TIFF'
>

Hi Axel,

Here is a new version, with hopefully this time the correct buildrequirements :

http://people.atrpms.net/~tverhoeven/agx-ast-addons-1.4.5-1.el5.src.rpm

I need to setup a mock env to test this stuff before sending it to
you, that would help reduce these errors :-)

Regards,
Tim

--
Tim Verhoeven - tim.verhoeven.be [at] gmail - 0479 / 88 11 83

Hoping the problem magically goes away by ignoring it is the
"microsoft approach to programming" and should never be allowed.
(Linus Torvalds)

_______________________________________________
atrpms-devel mailing list
atrpms-devel [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-devel


Axel.Thimm at ATrpms

Mar 22, 2008, 12:44 AM

Post #9 of 18 (4825 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
Hi,

On Fri, Mar 21, 2008 at 06:15:07PM +0100, Tim Verhoeven wrote:
> On Thu, Mar 20, 2008 at 1:35 PM, Axel Thimm <Axel.Thimm [at] atrpms> wrote:
> Here is a new version, with hopefully this time the correct buildrequirements :
>
> http://people.atrpms.net/~tverhoeven/agx-ast-addons-1.4.5-1.el5.src.rpm
>
> I need to setup a mock env to test this stuff before sending it to
> you, that would help reduce these errors :-)

Thanks, I added a small fix for x86_64 and it built on all distros (but
F9 where asterisk's build fails).
--
Axel.Thimm at ATrpms.net


Axel.Thimm at ATrpms

Aug 9, 2009, 1:00 AM

Post #10 of 18 (3395 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
Hi,

On Wed, Aug 05, 2009 at 02:04:31PM +0200, Tim Verhoeven wrote:
> I have again a set of updates (for Asterisk 1.4) available at
> http://people.atrpms.net/~tverhoeven/ :
>
> asterisk-1.4.25.1-78.el5.src.rpm
> asterisk-addons-1.4.9-23.el5.src.rpm
> dahdi-linux-2.2.0.2-61.el5.src.rpm
> dahdi-tools-2.2.0-58.el5.src.rpm
> libpri-1.4.10.1-24.el5.src.rpm
>
> I haven't build these myself since dl.atrpms.net and www.atrpms.net
> seemed to be down. But they should build fine since they are minor
> upgrades . If not, just let me know and I'll fix it.

Thanks, all rebuilt or merged in. I have a new set of asterisk-1.6
with asterisk-sounds packages that support both 1.4 and 1.6. I will
upload them as well and post something about them (they will go to
testing first due to the changes in 1.4/1.6 comatibility and
linuxpaths patch).
--
Axel.Thimm at ATrpms.net


tim.verhoeven.be at gmail

Aug 10, 2009, 3:17 AM

Post #11 of 18 (3395 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
On Sun, Aug 9, 2009 at 10:00 AM, Axel Thimm<Axel.Thimm [at] atrpms> wrote:
>
> Thanks, all rebuilt or merged in. I have a new set of asterisk-1.6
> with asterisk-sounds packages that support both 1.4 and 1.6. I will
> upload them as well and post something about them (they will go to
> testing first due to the changes in 1.4/1.6 comatibility and
> linuxpaths patch).

I've also just finished work on my 1.6 Asterisk and required packages.
They are currently all present on
http://people.atrpms.net/~tverhoeven/ :

asterisk-1.6.0.10-4.el5.src.rpm
libresample-0.1.3-0.el5.src.rpm
libedit-3.0-1.20090722cvs.el5.src.rpm
gsm-1.0.13-0.el5.src.rpm
uw-imap-2007e-1.el5.src.rpm
iksemel-1.4-0.el5.src.rpm
radiusclient-ng-0.5.6-0.el5.src.rpm

I've currently have this running on a small server with a couple of
users (pure SIP though) and it seems to run fine.

About the pwlib issues. I've started my package from the Fedora
Asterisk package so I find it strange that it would have a error on
that. The changes made to 1.4 for this seem to be present in in the
1.6 source be default. If there is still a error just send me the
complete buildlog and I'll check it out.

Regards,
Tim

--
Tim Verhoeven - tim.verhoeven.be [at] gmail - 0479 / 88 11 83

Hoping the problem magically goes away by ignoring it is the
"microsoft approach to programming" and should never be allowed.
(Linus Torvalds)

_______________________________________________
atrpms-devel mailing list
atrpms-devel [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-devel


Axel.Thimm at ATrpms

Aug 10, 2009, 2:43 PM

Post #12 of 18 (3395 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
Hi,

On Mon, Aug 10, 2009 at 12:17:29PM +0200, Tim Verhoeven wrote:
> On Sun, Aug 9, 2009 at 10:00 AM, Axel Thimm<Axel.Thimm [at] atrpms> wrote:
> >
> > Thanks, all rebuilt or merged in. I have a new set of asterisk-1.6
> > with asterisk-sounds packages that support both 1.4 and 1.6. I will
> > upload them as well and post something about them (they will go to
> > testing first due to the changes in 1.4/1.6 comatibility and
> > linuxpaths patch).
>
> I've also just finished work on my 1.6 Asterisk and required packages.
> They are currently all present on
> http://people.atrpms.net/~tverhoeven/ :

OK, this mail also came after I uploaded the asterisk bits. But I know
before even looking into the specfiles, that you've been more thorough
than me form the number of new src.rpms. :)

> asterisk-1.6.0.10-4.el5.src.rpm
> libresample-0.1.3-0.el5.src.rpm
> libedit-3.0-1.20090722cvs.el5.src.rpm
> gsm-1.0.13-0.el5.src.rpm
> uw-imap-2007e-1.el5.src.rpm
> iksemel-1.4-0.el5.src.rpm
> radiusclient-ng-0.5.6-0.el5.src.rpm
>
> I've currently have this running on a small server with a couple of
> users (pure SIP though) and it seems to run fine.

OK, I'll have to check the specfile changes and try to merge our
efforts. BTW why are you using 1.6.0.x and not 1.6.1.x?

> About the pwlib issues. I've started my package from the Fedora
> Asterisk package so I find it strange that it would have a error on
> that. The changes made to 1.4 for this seem to be present in in the
> 1.6 source be default. If there is still a error just send me the
> complete buildlog and I'll check it out.

My memory fails me, what where the pwlib issues?
--
Axel.Thimm at ATrpms.net


tim.verhoeven.be at gmail

Aug 11, 2009, 1:51 AM

Post #13 of 18 (3392 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
On Mon, Aug 10, 2009 at 11:43 PM, Axel Thimm<Axel.Thimm [at] atrpms> wrote:
>
> OK, I'll have to check the specfile changes and try to merge our
> efforts. BTW why are you using 1.6.0.x and not 1.6.1.x?

That is my CentOS background. I feel that the 1.6.1 branch is a bit to
new right now, so I will stick with the 1.6.0 one until 1.6.1 has
matured a bit more. IIRC there will be three 1.6 branches that will be
maintained at a certain time. So when 1.6.3 is out we will need to
move to 1.6.1 anyway.

>> About the pwlib issues. I've started my package from the Fedora
>> Asterisk package so I find it strange that it would have a error on
>> that. The changes made to 1.4 for this seem to be present in in the
>> 1.6 source be default. If there is still a error just send me the
>> complete buildlog and I'll check it out.
>
> My memory fails me, what where the pwlib issues?

Your mail from June 8 :
>> On Fedora it fails on the pwlib dependencies, which is an old issue
>> which I fixed some time ago in the 1.4 packages.

Regards,
Tim

--
Tim Verhoeven - tim.verhoeven.be [at] gmail - 0479 / 88 11 83

Hoping the problem magically goes away by ignoring it is the
"microsoft approach to programming" and should never be allowed.
(Linus Torvalds)

_______________________________________________
atrpms-devel mailing list
atrpms-devel [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-devel


Axel.Thimm at ATrpms

Aug 11, 2009, 4:13 AM

Post #14 of 18 (3391 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
Hi,

On Tue, Aug 11, 2009 at 10:51:15AM +0200, Tim Verhoeven wrote:
> On Mon, Aug 10, 2009 at 11:43 PM, Axel Thimm<Axel.Thimm [at] atrpms> wrote:
> >
> > OK, I'll have to check the specfile changes and try to merge our
> > efforts. BTW why are you using 1.6.0.x and not 1.6.1.x?
>
> That is my CentOS background. I feel that the 1.6.1 branch is a bit to
> new right now, so I will stick with the 1.6.0 one until 1.6.1 has
> matured a bit more.

Fair enough, I guess it will make sense to maintain both 1.6.0.x and
1.6.1.x since upstream does so. I don't think there are that many
differences as to packaging.

> IIRC there will be three 1.6 branches that will be
> maintained at a certain time. So when 1.6.3 is out we will need to
> move to 1.6.1 anyway.
>
> >> About the pwlib issues. I've started my package from the Fedora
> >> Asterisk package so I find it strange that it would have a error on
> >> that. The changes made to 1.4 for this seem to be present in in the
> >> 1.6 source be default. If there is still a error just send me the
> >> complete buildlog and I'll check it out.
> >
> > My memory fails me, what where the pwlib issues?
>
> Your mail from June 8 :
> >> On Fedora it fails on the pwlib dependencies, which is an old issue
> >> which I fixed some time ago in the 1.4 packages.

I still can't pin it down, but I checked the diffs and half a year agi
I just removed the pwlib dependencies (see below). IIRC (which I
don't), the pwlib-devel dependency was there only because opal-devel
or openh323-devel should had been pulling in pwlib-devel, and some
former vendor package was missing this dependency.

Bottom line: There is no need to depend on pwlib explicitely in
asterisk and it even harms builds whe opa is built again ptlib instead
of pwlib.

--- /usr/src/at/.archives/asterisk-1.4.24.1-74.spec 2009-04-13 20:11:10.000000000 +0200
+++ /usr/src/at/.archives/asterisk-1.4.24.1-75.spec 2009-04-21 10:47:41.000000000 +0200
@@ -15,7 +15,7 @@
Summary: The Open Source Linux PBX
Name: asterisk
Version: 1.4.24.1
-Release: 74%{?dist}
+Release: 75%{?dist}
Epoch: 1
License: GPL
Group: Applications/Internet
@@ -46,8 +46,8 @@
BuildRequires: libogg-devel, libvorbis-devel
BuildRequires: unixODBC-devel, libtool-ltdl-devel, sqlite-devel
%{?with_freedts:BuildRequires: freetds-devel}
-%{?with_opal:BuildRequires: pwlib-devel, opal-devel}
-%{?with_openh323:BuildRequires: pwlib-devel, openh323-devel}
+%{?with_opal:BuildRequires: opal-devel}
+%{?with_openh323:BuildRequires: openh323-devel}
BuildRequires: qt-devel, kdelibs-devel, gtk2-devel
%{?with_radiusclientng:BuildRequires: radiusclient-ng-devel}
BuildRequires: alsa-lib-devel
--
Axel.Thimm at ATrpms.net


tim.verhoeven.be at gmail

Aug 11, 2009, 5:55 AM

Post #15 of 18 (3391 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
On Tue, Aug 11, 2009 at 1:13 PM, Axel Thimm<Axel.Thimm [at] atrpms> wrote:
>
> Bottom line: There is no need to depend on pwlib explicitely in
> asterisk and it even harms builds whe opa is built again ptlib instead
> of pwlib.
>
> --- /usr/src/at/.archives/asterisk-1.4.24.1-74.spec     2009-04-13 20:11:10.000000000 +0200
> +++ /usr/src/at/.archives/asterisk-1.4.24.1-75.spec     2009-04-21 10:47:41.000000000 +0200
> @@ -15,7 +15,7 @@
>  Summary: The Open Source Linux PBX
>  Name: asterisk
>  Version: 1.4.24.1
> -Release: 74%{?dist}
> +Release: 75%{?dist}
>  Epoch: 1
>  License: GPL
>  Group: Applications/Internet
> @@ -46,8 +46,8 @@
>  BuildRequires: libogg-devel, libvorbis-devel
>  BuildRequires: unixODBC-devel, libtool-ltdl-devel, sqlite-devel
>  %{?with_freedts:BuildRequires: freetds-devel}
> -%{?with_opal:BuildRequires: pwlib-devel, opal-devel}
> -%{?with_openh323:BuildRequires: pwlib-devel, openh323-devel}
> +%{?with_opal:BuildRequires: opal-devel}
> +%{?with_openh323:BuildRequires: openh323-devel}
>  BuildRequires: qt-devel, kdelibs-devel, gtk2-devel
>  %{?with_radiusclientng:BuildRequires: radiusclient-ng-devel}
>  BuildRequires: alsa-lib-devel

Ok :-)

Trying to install on a test server here I've noticed that the stable
repo contains asterisk-addons 1.6.1. Does this package work with the
Asterisk 1.4 that is in the stable repo ? I'm guessing it belongs in
the bleeding repo.

So if we are going to maintain Asterisk 1.4, 1.6.0 and 1.6.1 at the
same time what are we going to do about the naming of the packages ?
Or create subrepos for each version ?

Regards,
Tim

--
Tim Verhoeven - tim.verhoeven.be [at] gmail - 0479 / 88 11 83

Hoping the problem magically goes away by ignoring it is the
"microsoft approach to programming" and should never be allowed.
(Linus Torvalds)

_______________________________________________
atrpms-devel mailing list
atrpms-devel [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-devel


Axel.Thimm at ATrpms

Aug 11, 2009, 7:50 AM

Post #16 of 18 (3384 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
On Tue, Aug 11, 2009 at 02:55:16PM +0200, Tim Verhoeven wrote:
> On Tue, Aug 11, 2009 at 1:13 PM, Axel Thimm<Axel.Thimm [at] atrpms> wrote:
> > Bottom line: There is no need to depend on pwlib explicitely in
> > asterisk and it even harms builds whe opa is built again ptlib instead
> > of pwlib.

OK, let's try again in english: "[...] when opal is built against
[...]" ...

> Ok :-)
>
> Trying to install on a test server here I've noticed that the stable
> repo contains asterisk-addons 1.6.1. Does this package work with the
> Asterisk 1.4 that is in the stable repo ? I'm guessing it belongs in
> the bleeding repo.
>
> So if we are going to maintain Asterisk 1.4, 1.6.0 and 1.6.1 at the
> same time what are we going to do about the naming of the packages ?
> Or create subrepos for each version ?

I don't know if they can really coexist, it would need a lot of work
to make asterisk14, asterisk161 and asterisk162 (or one of them taking
up the default asterisk namespace) to be installable in parallel.

We can either have different subrepos, which ATrpms never introduced
until now as for each similar project we would get more and more such
subrepos - but that doesn't mean it shouldn't be done now. Or have
them installed in the same repo and let yum install do the magic. At
least on Fedora yum install foo-oldversion works nicely by now
(e.g. yum allows you to specify an older version), but I don't know
whether the stock yum on RHEL5 and the CentOS yum already support
this.
--
Axel.Thimm at ATrpms.net


tim.verhoeven.be at gmail

Aug 11, 2009, 1:51 PM

Post #17 of 18 (3393 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
On Tue, Aug 11, 2009 at 4:50 PM, Axel Thimm<Axel.Thimm [at] atrpms> wrote:
>>
>> So if we are going to maintain Asterisk 1.4, 1.6.0 and 1.6.1 at the
>> same time what are we going to do about the naming of the packages ?
>> Or create subrepos for each version ?
>
> I don't know if they can really coexist, it would need a lot of work
> to make asterisk14, asterisk161 and asterisk162 (or one of them taking
> up the default asterisk namespace) to be installable in parallel.
>
> We can either have different subrepos, which ATrpms never introduced
> until now as for each similar project we would get more and more such
> subrepos - but that doesn't mean it shouldn't be done now. Or have
> them installed in the same repo and let yum install do the magic. At
> least on Fedora yum install foo-oldversion works nicely by now
> (e.g. yum allows you to specify an older version), but I don't know
> whether the stock yum on RHEL5 and the CentOS yum already support
> this.
>

I wasn't thinking to be able to install the different versions at the
same time. That would be taking it to far. It woud be just something
that allows users to keep a version without having to worry that a yum
update will upgrade their Asterisk to a new major version. The
Asterisk website also says that upgrading from 1.6.x to 1.6.x+1 should
be considered a major upgrade.

So what I was thinking is that we use plain "asterisk" for the latest
release there is at the moment (right now 1.6.1, and also let is
provide asterisk161) and use asterisk160 and asterisk14 for the older
version. They should conflict on each other (or how is that called in
RPM terms).

That way people using a older release can stay with it without fear of
getting upgraded unwantingly. And people with the latest version can
choose to stay with or move on if a newer major release is done.

Regards,
Tim

--
Tim Verhoeven - tim.verhoeven.be [at] gmail - 0479 / 88 11 83

Hoping the problem magically goes away by ignoring it is the
"microsoft approach to programming" and should never be allowed.
(Linus Torvalds)

_______________________________________________
atrpms-devel mailing list
atrpms-devel [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-devel


Axel.Thimm at ATrpms

Aug 12, 2009, 12:29 AM

Post #18 of 18 (3388 views)
Permalink
Re: Updates for Asterisk and co [In reply to]
Hi,

On Tue, Aug 11, 2009 at 10:51:37PM +0200, Tim Verhoeven wrote:
> So what I was thinking is that we use plain "asterisk" for the latest
> release there is at the moment (right now 1.6.1, and also let is
> provide asterisk161) and use asterisk160 and asterisk14 for the older
> version.

Yes, that makes a lot of sense.

> They should conflict on each other (or how is that called in
> RPM terms).

That's what its called (Conflicts: ... tag)

> That way people using a older release can stay with it without fear of
> getting upgraded unwantingly.

That's a great feature. So let's do asterisk, asterisk160 and
asterisk14. Currently I'm shaping up asterisk(161) and found out that
most changes also apply to the 1.4.x specfile. I'll finish this up and
we can check to see how to make the new packages.
--
Axel.Thimm at ATrpms.net

atrpms devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.