Bug 426490 - Include MySQL support from asterisk-addons
Include MySQL support from asterisk-addons
Product: Fedora
Classification: Fedora
Component: asterisk (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Jeffrey C. Ollie
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-12-21 10:23 EST by Anthony Messina
Modified: 2007-12-21 14:05 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-12-21 12:18:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Anthony Messina 2007-12-21 10:23:15 EST
Description of problem:
I am quite pleased to see Asterisk make it into the Fedora repo.  Thank you! 
Please include support for the MySQL functions of Asterisk from 
asterisk-addons (CLI functions, applications, cdr applications, etc.)

Version-Release number of selected component (if applicable):
I'd like to see these hit F7 and F8.

Without these functions, those of us who depend on MySQL<-->Asterisk 
integration won't be able to use your RPMs :(
Comment 1 Jeffrey C. Ollie 2007-12-21 12:18:52 EST
Unfortunately the asterisk-addons will need to be packaged separately, mainly
due to the licensing of MySQL.  It should be possible to compile asterisk-addons
against the asterisk-devel package.  If it isn't please file a bug and I'll see
what I can do to make the asterisk-devel package work for that purpose.
Comment 2 Anthony Messina 2007-12-21 13:11:47 EST
I hear this issue a lot, but I'm not sure I understand it and I apologize if 
this isn't the place for questions.  Doesn't CallWeaver has the MySQL code 
(callweaver-mysql)?  I don't see how that is different especially since Fedora 
packages mysql AND, now, asterisk.  Why would Fedora not be able to package 
the code that links them, since it's being done in CallWeaver, the code forked 
from Asterisk?

Again, I'm just asking.  And I do want to thank you for getting Asterisk into 
Comment 3 Jeffrey C. Ollie 2007-12-21 13:56:22 EST
This is from doc/mysql.txt from the Asterisk tarball:

	We were recently contacted by MySQL and informed that the MySQL client 
	libraries are now under GPL license and not LGPL license as before.  

	Since Asterisk does allow exceptions to GPL, we are removing MySQL support 
	from standard Asterisk.  We will, where appropriate, make it available via 
	a separate package which will only be usable when Asterisk is used completely
	within GPL (i.e. not in conjunction with G.729, OpenH.323, etc).  We 
	apologize for the confusion.

	You may find this in the new "asterisk-addons" package.

	Mark Spencer

OpenPBX/Callweaver added MySQL support back in after they forked from
Asterisk.  I don't recall the discussions but since CallWeaver is
"pure" GPL it's probably permissible for them to include it.  IANAL -
YMMV.  I don't have the time/interest right now for packaging anything
else right now but I'm willing to work with whomever would like to
package up asterisk-addons so that everything works.
Comment 4 Anthony Messina 2007-12-21 14:05:30 EST
Thank you very much.  That makes sense, though it's a bummer :(

I do understand your position.  Axel Thimm already packages asterisk and 
asterisk-addons at ATrpms.net. It WOULD be helpful if your asterisk packages 
would work with his asterisk-addons packages and vice versa, especially since 
many of us will need to use his zaptel/zaptel-kmdl packages since the zaptel 
kernel module is not upstream.

Again, thanks.  Have a good day.

Note You need to log in before you can comment on or make changes to this bug.