> I asked a somewhat similar question and got no response. Can majordomo
> 1.90 be installed in the existing 1.62 directory without changes to
> the aliases and config/resend files? Can I "upgrade" my lists one at
> a time?
Yes. I have this setup for testing new betas, but it works great for
integration once the new release is out too.
What I do is make a separate directory for the new stuff, called
/usr/local/majordomo-1.90. Make sure that wrapper and all your majordomo
files point to this new directory. Then set up aliases for majordomo
itself, called majordomo-1.90 or some such. Note that with the new
-request handling, users have very little need to mail to majordomo
directly, which helps limit confusion....
Now, I set up my lists, one at a time, and subscribe just me. The
"incoming" alias for the list consists of the old majordomo resend,
and the new 1.90 resend. This way, all incoming traffic goes through
the old setup, and sends me a message using the new setup. Then I can
compare the two messages. This is especially important for digests,
where it might take a few tries to get the new setup just right (in my
experience, anyway).
Here's a few lines from my alias file to show you what I mean:
> #
> # majordomo setup
> #
> majordomo: "|/usr/local/majordomo/wrapper majordomo"
> majordomo-owner: pdc
> owner-majordomo: pdc
>
> majordomo-beta: "|/usr/local/majordomo-1.90/wrapper majordomo"
> majordomo-beta-owner: pdc
> owner-majordomo-beta: majordomo-beta-owner
> mjd-test: majordomo-beta
>
> test-f-costume-digest: "| /local/majordomo-1.90/wrapper digest -r -C -l f-costume-digest test-f-costume-outgoing"
> test-f-costume-outgoing: pdc
>
> [...]
> f-costume: "|/usr/local/majordomo/wrapper resend -R -p bulk -M 50000 -l f-costume -f f-costume-owner -h lunch.asd.sgi.com -s f-costume-outgoing"
> f-costume-outgoing: :include:/usr/local/majordomo/lists/f-costume,
> f-costume-digestify, test-f-costume-digest
> [...]
--
Paul Close pdc@sgi.com ...!{ames, decwrl, uunet}!sgi!pdc
No fate but what we make
References:
|
|
