Adding Mhonarc to existing Mailman installation
I am building a new Mailman 2.1.9 installation tree, and want to configure it with Mhonarc and Mnogosearch. I notice that the Mhonarc patches change the config.pck version number from 96 to 96.2 because there seem to be some changes to the file definition.
I have signed up on the mmi mailman-mnogosearch mail list and see what's involved, but have mailman-specific questions.
What happens if I move a config.pck running on stock 2.1.9 (version 96) to this new tree? Is there something in Mailman that figures out how to remunge the config.pck file?
Hank
vancleef@lostwells.net wrote:
What happens if I move a config.pck running on stock 2.1.9 (version 96) to this new tree? Is there something in Mailman that figures out how to remunge the config.pck file?
Yes! This is the key to migrating a list to a new version in any context. See the definition of CheckVersion() in Mailman/MailList.py.
Whenever a list is loaded from config.pck (or even a 2.0.x config.db), the data version from the file is compared to the version of the installation, and if it is less, Update is imported from Mailman/versions.py and called to migrate the list data to the current version. This is why you can drop a config.pck from an older version into a running newer version and it just works.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
vancleef＠lostwells.net