Re: user-friendly app, plugin & rules loading & updating

[Justin Mason <jm...@jmason.org>]

OpenMacNews writes:
> reading with interest the ongoing thoughts/discussion about v32x 
> planning, rules mgmt, etc.
> 
> wearing my user hat (which is usually glued-on, anyway ...), i did a 
> bit of "wish it could ..."
> 
> 1st caveat:  this no doubt ignores, and tramples upon, some combination 
> of common-sense, what already exists, and future code-planning. that 
> said ...
> 
> as a user, i upgrade the app, plugins (some 'core', some not) and rules 
> (again, some core, come not) on a regular, often asynch, basis.
> 
> in an ideal world, i'd like to see some consistency in/across
> 
> (1) config files
> (2) upgrade methods
> 
> e.g.,
> 
> (a) app conf in 'local.cf' (the usual location hierarchy)
> (b) plugin loading *only* in, say, "plugins.conf", wherein its the 
> resonsibility of the end-user to move/copy the appropriate plugin 
> identities & locations FROM the *.pre's
> (c) rule-sets loading *only* in, say, "rules.conf".  i.e., turning 
> on/off a rules set is no longer a matter of dropping the *.cf into the 
> dir, but rather done in a parseable conf file.
> 
> that way, i don't worry abt "what's lying around" or in some errant 
> directory, but rather *just* what i've explicitly enable in one place 
> ...
> 
> and, then, upgrades to any/all would be via:
> 
> 	sa-update-app
> 	sa-update-plugins
> 	sa-update-rules

fwiw, apache2 on Ubuntu does this pretty nicely these days...

--j.