|Summary:||ASTERISK-11494: Leftover modules from 1.4 will crash 1.6 ..|
|Reporter:||Danny Messano (drmessano)||Labels:|
|Date Opened:||2008-02-22 01:15:31.000-0600||Date Closed:||2011-06-07 14:00:32|
|Description:||The following modules, leftover from 1.4, will crash 1.6 on startup:|
****** ADDITIONAL INFORMATION ******
With the existing noload statements in the modules.conf for the following:
...and the addition of now 10 more modules that should probably be excluded, it may be a good idea to add some sort of module cleanup to the install process.
|Comments:||By: Michiel van Baak (mvanbaak) 2008-02-22 01:19:05.000-0600|
'make install' already warns you about this.
By: Danny Messano (drmessano) 2008-02-22 02:14:11.000-0600
Considering that these were not 3rd party modules, but an actual part of 1.4, they should be addressed differently than the canned warning. There's no reason that KNOWN, formerly included modules, can't be addressed, with 3rd party modules left to the user to sort out.
If you are going to address a handful of older modules with noload statements in modules.conf, and now pass off leftover modules from 1.4 with "there's a warning", then you're creating an inconsistency.
By: Joshua C. Colp (jcolp) 2008-02-22 08:23:25.000-0600
The current modules.conf sample doesn't actually noload any of the modules you talked about above, you are looking at quite an old file.
By: Tilghman Lesher (tilghman) 2008-02-22 09:52:33.000-0600
You can quite easily solve this by first doing a 'make uninstall' prior to your 'make install'.
By: Danny Messano (drmessano) 2008-02-22 10:22:47.000-0600
If the overall consensus is that one should just figure it out, then that's fine.. but IMO, a note to run "make uninstall" or SOMETHING should be noted SOMEWHERE for those that are upgrading.
By: Tilghman Lesher (tilghman) 2008-02-22 10:31:11.000-0600
As mvanbaak correctly noted initially, it warns you. If you choose to ignore warnings, well, that's your choice, but you cannot say that we did not notify you of a problem.