You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2006/10/14 23:21:15 UTC

[Bug 5130] using sa-update for plugins

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5130





------- Additional Comments From felicity@apache.org  2006-10-14 14:21 -------
(In reply to comment #0)
> Based on the discussion at ApacheCon, a few suggestions for sa-update and plugins:
> 1.  Rules requiring plugins should be distributed using sa-update, but surounded
> with ifplugin ... endif blocks

Yes, that already has to be the case.

> 2.  an additional command-line option to sa-update should be added to allow
> downloading plugins, something like `sa-update --download-plugins`  The thought
> here is that an administrator is less likely to script that command, but would
> type it interactively and supervise the code being installed.

It's a possibility.  Right now that option would be the default fwiw.

> 3.  as an optional feature, a cpan-like facility could be added that would allow
> querying the plugin library for new plugins or newer versions of plugins, so
> that `sa-update --list-new-plugins` would provide a list of plugins either not
> installed or with newer available versions, and `sa-update --download-one-plugin
> foo` would download just the foo plugin.

sa-update doesn't really work like that.  Either you download the channel update
or you don't.  There isn't a concept of having a channel with multiple files w/
different versions that you can choose from.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.