[EMAIL PROTECTED] 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 [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp