-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm happy with the "sa-check" idea, as long as we keep a "spamassassin"
wrapper that just does an exec(). easy enough, and very sensible.
+1
I think the POD docs from "spamassassin" should be split into the
"sa-check" POD and whatever other "sa-blah" scripts we come up with
from that.
also, +1 on Michael's "sa-history" script idea.
however the cvs/svn style, I'm not fond of. reasons:
- without require-ish hacking, it'll mean all the commands
would get "use"'d -- increasing RAM usage. I'd prefer to
avoid that.
- having multiple commands as "prefix-command", e.g. "sa-learn",
"sa-check" etc. is good as a UNIX UI -- "sa-<tab>" to get the list
of possible commands.
- the POD file for that one wrapper would be gigantic and unusable.
we could go for an svn-style "spamassassin help", but then we'd have
to write our own documentation-reading subsystem, which seems like
wasted effort when POD is already there and already working nicely
on all platforms.
also, TBH I find that kind of subsystem to be an annoying UI -- do I
read the man page? do I type "blah help"? "blah help commands"?
etc.
- --j.
Malte S. Stretz writes:
> On Sunday 23 January 2005 00:22 CET Daniel Quinlan wrote:
> > I've been thinking about bug 3635.
> >
> > One idea:
> >
> > rename "spamassassin" to "sa-check"
> > make "spamassassin" a meta document that execs sa-check for backwards
> > compatibility
> >
> > Another idea:
> >
> > make "spamassassin" a meta document that execs sa-check for backwards
> > compatibility
> > move spamassassin pod to "spamassassinrun" document
>
> Yet another idea:
>
> make "spamassassin" a caller for all tools, a bit like the cvs commands.
> Like this:
> old | new | calls
> -----------------------+----------------------+----------------
> spamassassin | spamassassin check | sa-check
> sa-learn | spamassassin learn | sa-learn
> spamassassin -r | spamassassin report | sa-report
> spamassassin -d | spamassassin clean | ...
>
> All sub-commands could be moved to /usr/lib/spamassassin (and out of $PATH
> when some compatibility flag is disabled) at some point.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFB9dKqMJF5cimLx9ARAnFrAJ4jZADFAFpatVb3Qv43wzPxIdrIiACfUctg
+oUJccV9ZM55PI5MhRJUHfI=
=Yw+C
-----END PGP SIGNATURE-----
