[Home]

Summary:ASTERISK-17691: [patch] Start migrating unsupported modules to separate unsupported/ directory
Reporter:Leif Madsen (lmadsen)Labels:
Date Opened:2011-04-13 13:55:03Date Closed:2011-07-20 13:30:19
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/BuildSystem
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) __20110413-asterisk-1.8-unsupported-modules.txt
( 1) __20110413-asterisk-trunk-unsupported-modules.txt
Description:There are several modules that receive no support from the community currently, or are deprecated and have alternative modules you should be using. This issue is the place for patches and tracking the modules that will be marked as (UNSUPPORTED).

In Asterisk 1.8 we can't make too many changes, but we can certainly change the description of modules to show that they are (UNSUPPORTED) and mark them to not build by default.

In Asterisk trunk (1.10) we'll move these modules to an unsupported directory, much like we have the addons directory. These modules will then be grouped into that directory.
Comments:By: Leif Madsen (lmadsen) 2011-04-13 13:56:08

Marking as confirmed as not all the work has been done yet, but this is a start.

By: Leif Madsen (lmadsen) 2011-04-13 15:43:53

Now that I've got the trunk version done, I'm moving this to Ready For Testing.

By: Leif Madsen (lmadsen) 2011-04-14 14:47:06

After additional discussion on IRC with russell and kpfleming, a different approach (which is less intrusive to those building packages) has been proposed. I've created a wiki page which outlines the proposed approach. Any comments are welcome.

https://wiki.asterisk.org/wiki/display/~lmadsen/Asterisk+Module+Support+States

By: Leif Madsen (lmadsen) 2011-07-20 13:30:19.360-0500

This has been completed.