Front page | perl.qpsmtpd |
Postings from September 2007
> From: =?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?= <ask@develooper.com>
> Date: Thu, 6 Sep 2007 00:49:06 -0700
>
>
> On Sep 5, 2007, at 3:27 PM, Chris Garrigues wrote:
>
> > okay...you've demonstrated that the other more sensible way works
> > fine...so why
> > does the default distribution do it the way it does?
>
> Isn't it mostly a matter of poor naming ? Those plugins were some of
> the first ones when we weren't so wise, yet.
>
> Renaming them is tricky because we'll break a bunch of old
> configuration files.
>
> Some of this will be easier to fix if if let plugins register to be
> run "first" and "last".
I just had a thought that it may make sense to do something like the prcsys
stuff where rc files specify dependencies on other rc files.
They could have rules like:
This plugin requires that plugin X run (before|after) it runs.
If plugin X is also installed, it must run (before|after) this plugin.
This plugin is incompatible with plugin X.
The plugins could also have some degree of provides/requires data, so we could
have (for example) a plugin that requires whitelists and a variety of plugins
that provide whitelists. Throw in version numbers and it starts to look like
what RPM does with dependencies.
Backwards compatibility might be difficult or impossible to provide when
implementing such schemes, but if you have to break backwards compatibility,
it's better to do that in a 0.x release than to wait.
> > Is there a roadmap which states when along the way the distribution
> > will include fixes like this one and
> > some documentation on the use of notes for whitelists and other
> > stuff like
> > that?
>
> The plan is, eventually, to have proper APIs and plugin hooks for
> some of the things notes are used for now (whitelists, user
> information, ....).
>
> And yes, definitely before "1.0".
>
>
>
> - ask
>
> --
> http://develooper.com/ - http://askask.com/
>
>
--
Chris Garrigues Trinsic Solutions
President 710-B West 14th Street
Austin, TX 78701-1798
http://www.trinsics.com/blog
http://www.trinsics.com 512-322-0180
Would you rather proactively pay for
uptime or reactively pay for downtime?
Trinsic Solutions
Your Trusted Friends in Proactive IT.
Thread Previous
|
Thread Next