On 3/25/2005 19:32, "Terry Allen" <[EMAIL PROTECTED]> wrote:
>> I suspect that Mailman 2.x to 3.x will not be that rough. Yes, the > > Hi again, > Just out of interest, on Postfix, there is a simple option to > upgrade a running system like so (as most here will know): > > make > stop postfix > make upgrade > start postfix > > I have never had to upgrade Mailman, as I started out using > it on 2.1.5 - is the upgrade procedure for Mailman anything like > Postfix? It's been foolproof thus far for me, so I'm hoping it works > as well on Mailman when the time comes. Well, it's basically that. (The 2.0x to 2.1x jump for us involved a change of servers, and server locations, and a huge jump in Linux version, so we couldn't do the straighforward install the new over the old and turn it on.) Unless one uses RedHat's RPMs...which will soon move things Mailman around considerably. That's probably a good thing...having configuration mixed with code mixed with data is not really a good idea. RedHat's new arrangement looks a lot better to me--I might well copy it even if I don't use the RPMs. And even with all the changes, the process will essentially involve copying the stuff in $prefix/lists and $prefix/archives (and maybe something else) to the right new places. Having configuration *be* code, while a nice use of Python's capabilities, also presents problems to those who believe that code and configuration should be disjoint...RedHat has managed it without bending *too* much. --John ------------------------------------------------------ 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=show&file=faq01.027.htp
