eval { use Some::Required::Module };

[Radoslaw Zielinski <ra...@gmail.com>]

Quoting sa-update:

  # These are the non-standard required modules
  # Use the evals to avoid the annoying RPM requirement check
  eval { use Net::DNS; };
  eval { use LWP::UserAgent; };
  eval { use HTTP::Date qw(time2str); };
  eval { use Archive::Tar; };
  eval { use IO::Zlib; };

Would someone bother to enlighten me: why break a dependency generator,
when it works exactly as intended?

Also, why would one describe one of the key features of RPM
(dependencies) as ``annoying''?  I mean, there's always a solution:

  echo "alias rpm='rpm --nodeps'" >> ~/.profile

-- 
Radosław Zieliński <ra...@pld-linux.org>

Re: eval { use Some::Required::Module };

[Radoslaw Zielinski <ra...@gmail.com>]

Theo Van Dinter <fe...@apache.org> [19-07-2006 21:46]:
> On Wed, Jul 19, 2006 at 09:38:54PM +0200, Radoslaw Zielinski wrote:
>>   # These are the non-standard required modules
>>   # Use the evals to avoid the annoying RPM requirement check
>>   eval { use Net::DNS; };
[...]
>> Would someone bother to enlighten me: why break a dependency generator,
>> when it works exactly as intended?
> The problem is that sa-update, and therefore the modules that are solely
> required by sa-update, are optional.  We don't want the spamassassin RPM to
> require perl(Archive::Tar), perl(IO::Zlib), etc.

> Arguably, sa-update could be made into its own RPM, and therefore have its own
> requirement list, but we haven't done that.

Bug #5003.

> Related is the problem of our
> package names versus distribution's package names, and places like RedHat
> "Obsolete"ing our packages because they want it done a different way, etc.

It's RH's problem, if a problem at all.  This *.spec is optional, after
all...

-- 
Radosław Zieliński <ra...@pld-linux.org>

HTML_SHORT_LENGTH EQUIV?

["Kevin A. McGrail" <ke...@thoughtworthy.com>]

Wondering if there is a "variable" or test available to simply use the 
length of the email body in rules?

If not, my thoughts are a test like

BODY_LENGTH_512 would test for the BODY_LENGTH > 512 bytes, 
HTML_BODY_LENGTH_512 would do the same using html_eval instead. Ideally, it 
would exclude images.

Anyone?
KAM 

Re: eval { use Some::Required::Module };

[Theo Van Dinter <fe...@apache.org>]

On Wed, Jul 19, 2006 at 09:38:54PM +0200, Radoslaw Zielinski wrote:
>   # These are the non-standard required modules
>   # Use the evals to avoid the annoying RPM requirement check
>   eval { use Net::DNS; };
>   eval { use LWP::UserAgent; };
>   eval { use HTTP::Date qw(time2str); };
>   eval { use Archive::Tar; };
>   eval { use IO::Zlib; };
> 
> Would someone bother to enlighten me: why break a dependency generator,
> when it works exactly as intended?

The problem is that sa-update, and therefore the modules that are solely
required by sa-update, are optional.  We don't want the spamassassin RPM to
require perl(Archive::Tar), perl(IO::Zlib), etc.

Arguably, sa-update could be made into its own RPM, and therefore have its own
requirement list, but we haven't done that.  Related is the problem of our
package names versus distribution's package names, and places like RedHat
"Obsolete"ing our packages because they want it done a different way, etc.

-- 
Randomly Generated Tagline:
"2. Your on-line shopping cart overflows and you get directed to the
  '12 items or more' checkout."
         - Top Ten Clues You Have Been Spending Too Much Time Shopping On-line