Bug 5130 - using sa-update for plugins
Summary: using sa-update for plugins
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: sa-update (show other bugs)
Version: 3.1.7
Hardware: All Linux
: P5 enhancement
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-14 03:24 UTC by Daniel J McDonald
Modified: 2006-12-04 11:47 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel J McDonald 2006-10-14 03:24:23 UTC 
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
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.
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.
Comment 1 Theo Van Dinter 2006-10-14 14:21:15 UTC 
(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.
Comment 2 Theo Van Dinter 2006-12-04 11:47:30 UTC 
I think the current sa-update system works fine with plugins, so I'm going to
call this WFM.