http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4824
Summary: build/mkrules will not enable rules that require a
plugin from sandbox unless file is in MANIFEST
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: minor
Priority: P5
Component: Building & Packaging
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
build/mkrules won't copy a "loadplugin" line from rulesrc/sandbox/*/*.cf unless
the plugin's .pm file is listed in MANIFEST. However, does this really make
sense for sandbox rules that are not expected to be publishable?
IMO, they should be allowed to be in rules/70_sandbox.cf in some way, for
testing, without being in MANIFEST.
I'm not sure how to deal with the other requirements for a rule that is in
testing -- for example, the MANIFEST check was put in to ensure that "make
disttest" can still pass, including --lint. perhaps what's needed is a new
configuration keyword similar to "loadplugin" which, however, implies that
failures to find the .pm file, should be considered nonfatal.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
