On Aug 7, 2009, at 10:46 AM, Adam McGreggor wrote:
*shimmied over to mailman-devs* (from -users)
Thanks!
On Fri, Aug 07, 2009 at 10:33:06AM -0400, Barry Warsaw wrote:It kind of sucks that there are so many other Mailman command line scripts, which is one reason why I've always put them in a separate Mailman specific bin directory. With MM3 though I intend to use a 'subcommand' approach so that there's only one 'mailman' command. Think things like 'mailman listmembers foo'. I'll probably keep mailmanctl separate though I haven't decided about that yet.Would it too much to ask for the 'old' (read 'current') scripts/ commandsto be aliased: at least in the first few releases? e.g., for 'list_members' to link to 'mailman listmembers' Perhaps as an install/configure/compilation option? "Create old-style links?" --old-style-links (maybe that's more for people who package: ISTR a couple of packagers are on list, yes?) (wonders how many other people have scripts that would need re-writing otherwise...)
There won't be a cmmi recipe for MM3 (no configure; make; make install) at least from upstream, but I'm happy to work with distros to figure out the right way to package Mailman 3.
As for aliases, I think it won't be worth it. I also want to standardize and make consistent all the command line options so that the whole suite of commands makes more sense.
-Barry
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
