-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Daniel Quinlan writes: > Michael Parker <[EMAIL PROTECTED]> writes: > > > Now you're adding in a whole other subsystem. Using this logic, it is > > pretty easy to argue that everything should be in one executable, and > > not split out. A little cross use is allowed. Here is my proposed > > set of commands and their arguments: > > > [...usages removed...] > > sa-filter > > sa-report > > sa-learn (maybe sa-bayes) > > sa-update > > sa-history/sa-awl (maybe sa-whitelist) > > sa-lint > > Hmmm... my thinking is that we have several basic actions people > perform. > > - filtering and removal of markup > - learning/forgetting > - reporting/revoking > - plugin-specific stuff that cannot be generalized > > I'd strongly favor move the basic learn functionality (learn, forget) > into a single command regardless of the learning subsystem and the > plugin-specific stuff like bayes, whitelist, and history into > plugin-specific commands. I agree with Daniel that we should model the command line UI around the use cases, not around the code subsystems involved. But then "plugin-specific stuff like bayes" -- Daniel, I'm not sure what you mean here, this seems to contradict the previous idea (UI based on use-cases). Regarding the idea of splitting plugin-specific stuff into its own command-line UI, I'm not sure I can go for that. For one thing, having two command-line APIs to control Bayes seems confusing; for another, the plugins should hook into the *existing* user interface, not create new, plugin-specific UIs that'll only work with that plugin. If we do the latter, we'll wind up down the road with multiple, conflicting scripts that are nearly the same in UI, but not quite, for each different plugin of a given type. On another aspect --- I like Michael's idea of leaving the "spamassassin" script's UI intact as it is now for a few 3.x releases. There is a lot of third-party code that hooks into SpamAssassin that will need to be updated before that interface can be removed safely without causing a lot of needless pain. - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFCG3MiMJF5cimLx9ARAo9SAKCjP2+ePv4nC7Zj9v7v+g0UcMkiRACdFL+Z NpfYw6kTNCyUIldvM5Giq2A= =rnNj -----END PGP SIGNATURE-----
