asterisk

Commit Graph

Author	SHA1	Message	Date
Automerge script	8aef9fdedd	Merged revisions 369005 via svnmerge from file:///srv/subversion/repos/asterisk/branches/10 ................ r369005 \| kpfleming \| 2012-06-15 11:07:08 -0500 (Fri, 15 Jun 2012) \| 22 lines Multiple revisions 369001-369002 ........ r369001 \| kpfleming \| 2012-06-15 10:56:08 -0500 (Fri, 15 Jun 2012) \| 11 lines Add support-level indications to many more source files. Since we now have tools that scan through the source tree looking for files with specific support levels, we need to ensure that every file that is a component of a 'core' or 'extended' module (or the main Asterisk binary) is explicitly marked with its support level. This patch adds support-level indications to many more source files in tree, but avoids adding them to third-party libraries that are included in the tree and to source files that don't end up involved in Asterisk itself. ........ r369002 \| kpfleming \| 2012-06-15 10:57:14 -0500 (Fri, 15 Jun 2012) \| 3 lines Add a script to enable finding source files without support-levels defined. ........ Merged revisions 369001-369002 from http://svn.asterisk.org/svn/asterisk/branches/1.8 ................ git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/10-digiumphones@369023 65c4cc65-6c06-0410-ace0-fbb531ad65f3	14 years ago
Terry Wilson	f0c8b18c18	Use older functions out of deference to older distros git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@326750 65c4cc65-6c06-0410-ace0-fbb531ad65f3	15 years ago
Terry Wilson	efd040cd11	Replace Berkeley DB with SQLite 3 There were some bugs in the very ancient version of Berkeley DB that Asterisk used. Instead of spending the time tracking down the bugs in the Berkeley code we move to the much better documented SQLite 3. Conversion of the old astdb happens at runtime by running the included astdb2sqlite3 utility. The ast_db API with SQLite 3 backend should behave identically to the old Berkeley backend, but in the future we could offer a much more robust interface. We do not include the SQLite 3 library in the source tree, but instead rely upon the distribution-provided libraries. SQLite is so ubiquitous that this should not place undue burden on administrators. git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@326589 65c4cc65-6c06-0410-ace0-fbb531ad65f3	15 years ago

Author

SHA1

Message

Date

Automerge script

8aef9fdedd

Merged revisions 369005 via svnmerge from

file:///srv/subversion/repos/asterisk/branches/10

................
  r369005 | kpfleming | 2012-06-15 11:07:08 -0500 (Fri, 15 Jun 2012) | 22 lines
  
  Multiple revisions 369001-369002
  
  ........
    r369001 | kpfleming | 2012-06-15 10:56:08 -0500 (Fri, 15 Jun 2012) | 11 lines
    
    Add support-level indications to many more source files.
    
    Since we now have tools that scan through the source tree looking for files
    with specific support levels, we need to ensure that every file that is
    a component of a 'core' or 'extended' module (or the main Asterisk binary)
    is explicitly marked with its support level. This patch adds support-level
    indications to many more source files in tree, but avoids adding them to
    third-party libraries that are included in the tree and to source files
    that don't end up involved in Asterisk itself.
  ........
    r369002 | kpfleming | 2012-06-15 10:57:14 -0500 (Fri, 15 Jun 2012) | 3 lines
    
    Add a script to enable finding source files without support-levels defined.
  ........
  
  Merged revisions 369001-369002 from http://svn.asterisk.org/svn/asterisk/branches/1.8
................


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/10-digiumphones@369023 65c4cc65-6c06-0410-ace0-fbb531ad65f3

Terry Wilson

f0c8b18c18

Use older functions out of deference to older distros

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@326750 65c4cc65-6c06-0410-ace0-fbb531ad65f3

Terry Wilson

efd040cd11

Replace Berkeley DB with SQLite 3

There were some bugs in the very ancient version of Berkeley DB that Asterisk
used. Instead of spending the time tracking down the bugs in the Berkeley code
we move to the much better documented SQLite 3.

Conversion of the old astdb happens at runtime by running the included
astdb2sqlite3 utility. The ast_db API with SQLite 3 backend should behave
identically to the old Berkeley backend, but in the future we could offer a
much more robust interface.

We do not include the SQLite 3 library in the source tree, but instead rely
upon the distribution-provided libraries. SQLite is so ubiquitous that this
should not place undue burden on administrators.


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@326589 65c4cc65-6c06-0410-ace0-fbb531ad65f3

3 Commits (33ce9ae08e85ceabd179c8bdef108d1ff5778ad2)