I was reading the wiki which says there's no good central repository for
plugins. Is there a reason why CPAN can't be used for qpsmtpd and its
plugins? Catalyst, CGI::Application and POE all have numerous plugins /
components on CPAN. SpamAssassin also uses CPAN. Just curious.
John
Hi
I know this must be a very common question, but
where could I send some plugins?
Last mails about this are the "what kind of structures do we use for storing
them"
But maybe we have this information and I didn't searched hard enought
I have written some plugins (whith its perldoc) (I'm shure
John Wang wrote:
I was reading the wiki which says there's no good central repository for
plugins. Is there a reason why CPAN can't be used for qpsmtpd and its
plugins? Catalyst, CGI::Application and POE all have numerous plugins /
components on CPAN. SpamAssassin also uses CPAN. Just curious.
On 2006-04-20 16:25:43 -0300, Leonardo Helman wrote:
> I know this must be a very common question, but
> where could I send some plugins?
> Last mails about this are the "what kind of structures do we use for storing
> them"
AFAIK that's where the discussion ended.
There is a plugins page on th
On Apr 21, 2006, at 09:17, Peter J. Holzer wrote:
There is a plugins page on the Wiki: http://wiki.qpsmtpd.org/plugins
Until we have a better place just add your plugins to the page.
This has probably been asked before, but why not add support for
plugins in a namespace, such as Qpsmtpd::Pl
On 4/21/06, David Wheeler <[EMAIL PROTECTED]> wrote:
>
> On Apr 21, 2006, at 09:17, Peter J. Holzer wrote:
>
> > There is a plugins page on the Wiki: http://wiki.qpsmtpd.org/plugins
> > Until we have a better place just add your plugins to the page.
>
> This has probably been asked before, but why
John Wang wrote:
I'm in favor of this. There seems to be some installer issues putting
qpsmtpd itself on CPAN but I think allowing plugins to be put on CPAN would
be a great help to getting more plugins out there. Getting plugins into the
Qpsmtpd::Plugin namespace would be a good first step.
Th
On Apr 21, 2006, at 10:28, John Peacock wrote:
The same issue that applies to qpsmtpd applies to the plugins. The
plugin files themselves are *not* complete modules, and cannot be
as they are stuffed into the appropriate place in the heirarchy
when loaded. You would be unable to install i
David Wheeler wrote:
I don't see why not. I mean, AFAICT, the problem would be testing. And
for that, I expect that it wouldn't be too hard to mock up Qpsmtpd for
testing the plugins. No?
PAUSE requires a package name and a $VERSION, neither of which exist in
any current plugins (although it
On Apr 21, 2006, at 11:17, John Peacock wrote:
PAUSE requires a package name and a $VERSION, neither of which
exist in any current plugins (although it is apparently possible to
add them and have the plugin still function). There is the [minor]
issue of having to sign up for a PAUSE accoun
10 matches
Mail list logo
