On Wed, Apr 12, 2006 at 10:17:34PM -0400, David F. Skoll wrote:
One idea would be to make some very small part of MIMEDefang into a
CPAN module, and let that module's build script automatically get the
truly required Perl modules.
Yes, that's a good idea. But if we did that, I would
On 13 Jan 2006 at 19:28, David F. Skoll wrote:
One of the biggest complaints from
people who've tried MIMEDefang is the number of Perl modules it
requires. I really hesitate to make another absolute dependency; I'd
rather continue to use the mechanism in
Jeff Rife wrote:
One idea would be to make some very small part of MIMEDefang into a
CPAN module, and let that module's build script automatically get the
truly required Perl modules.
Yes, that's a good idea. But if we did that, I would throw out most
of the existing code and rewrite
On Fri, 13 Jan 2006, David F. Skoll wrote:
[snip]
is probably not in the cards. One of the biggest complaints from
people who've tried MIMEDefang is the number of Perl modules it
requires.
[snip]
These people have obviously never installed RT :)
MIMEDefangs' pre-requisites are perfectly
Philip Prindeville wrote:
I suppose for people using RPM's with yum or smart, it might be different.
The best way to handle that is to package the different filters in their
own RPMs, and then *those* RPMs can specify the correct dependencies.
So you know that if you want to use
nathan r. hruby wrote:
These people have obviously never installed RT :)
Heh! We use RT here.
Actually, if you really want to discover some dependency hell, try
Catalyst plus Template Toolkit. Catalyst is a wonderful MVC-based Web
development suite---gorgeous to use, but an absolute bear to
I'd like to propose the following patch, as a prequel to the
posting of an amended mimedefang-filter on the Wiki...
--- redhat/mimedefang-spec.in.bak 2004-09-21 19:50:36.0 -0600
+++ redhat/mimedefang-spec.in 2006-01-13 15:51:55.0 -0700
@@ -138,16 +138,17 @@ Release:
On Fri, 2006-01-13 at 15:54 -0700, Philip Prindeville wrote:
I'd like to propose the following patch, as a prequel to the
posting of an amended mimedefang-filter on the Wiki...
If your changes are only going on the Wiki, then adding a Requires to
the mimedefang package is incorrect.
Richard
If your filter example post to the Wiki requires Net-CIDR-Lite, state that in
your Wiki entry. Those who want to use your code can load the module.
IMHO, the spec file, should only require packages that are truly required by
MIMEDefang, not packages that are popular extras in local filters.
Richard Laager wrote:
On Fri, 2006-01-13 at 15:54 -0700, Philip Prindeville wrote:
I'd like to propose the following patch, as a prequel to the
posting of an amended mimedefang-filter on the Wiki...
If your changes are only going on the Wiki, then adding a Requires to
the mimedefang
Philip Prindeville wrote:
I'm hoping that the .spec changes will mesh with the support for
filter_helo and the basic scripting for it that will be in the
future release that includes it.
filter_helo is one thing, but adding a dependency on Net::CIDR::Lite
is probably not in the cards. One of
Well, the question then becomes is should the shipped .spec file support
all of the example config files and scripts as well?
-Philip
Damrose, Mark wrote:
If your filter example post to the Wiki requires Net-CIDR-Lite, state that in
your Wiki entry. Those who want to use your code can load
Philip wrote:
Well, the question then becomes is should the shipped .spec file
support all of the example config files and scripts as well?
I think of the example config files and scripts as serving suggestions whose
caloric content is not included in the nutrition facts. ;)
--
No. MD is a framework and an Opensource one at that. People looking for a
cookie cutter approach who don't know perl should by CanIt.
Well, the question then becomes is should the shipped .spec file support
all of the example config files and scripts as well?
David F. Skoll wrote:
filter_helo is one thing, but adding a dependency on Net::CIDR::Lite
is probably not in the cards. One of the biggest complaints from
people who've tried MIMEDefang is the number of Perl modules it
requires. I really hesitate to make another absolute dependency; I'd
.
This patch adds support for MIMEDefang 2.49 to use 'virobot' to
filter virus. It modifies two files: configure.in, which adds the
'--disable-hauri' option to configure; and mimedefang.pl.in, including
three routines: entity_contains_virus_hauri(),
message_contains_virus_hauri
16 matches
Mail list logo
