-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
haraka-plugin-geoip-lite #50
Comments
Also here, in a separate branch. |
Hm ... not sure what your strategy here is but how do you consistently keep track of changes to shared code between the two? The PR I submitted yesterday for example didn't fix my problem since I am using the lite version which is still unpatched. |
Oh boy. A cluster has been made of this.
Short answer, I don't. The lite version hadn't been updated in ... a very long time. So after merging your other PR (which I now realize was in error, because the
It should have broken it! I misread the PR thinking you were removing the haraka-plugin prefix. What version of Haraka are you running? I'm reducing the diffs between the two plugins again, so that one can see the differences between them easily with |
I am running Haraka
|
that shouldn't work, but |
Check your config/plugins contents. Make sure you list the plugin as |
Regarding your previous comment, but isn't it weird then that |
Not if that's how you have it listed in |
I am confused ... so I thought I have to put the actual package name of the plugin into |
the latter |
Okay, gotcha. This still does not explain why |
It does. That line doesn't update the plugin name property. I think this patch would make it behave a little more like people expect: diff --git a/plugins.js b/plugins.js
index d30daf44..9dea5142 100644
--- a/plugins.js
+++ b/plugins.js
@@ -61,6 +61,7 @@ class Plugin {
let name = plugin.name;
if (/^haraka-plugin-/.test(name)) {
name = name.replace(/^haraka-plugin-/, '');
+ plugin.name = name;
}
let paths = []; Caution: not tested. |
Right, or simply.
However, this would require a patch in haraka core?! |
yep |
I wonder now if it wouldn't be way more transparent to everyone (especially third party plugins) if the name of a plugin will just be it's name and not somehow magically mangled inside the plugin system, what do you think? Edit: Especially since now it's kinda weird. From my understanding you have to call it |
There are many references to plugin names from other plugins. For example, the dmarc plugin fetches results from SPF and DKIM plugins. The watch plugin fetches results from many plugins. Most |
* plugins: also strip haraka-plugin- prefix from plugin.name, see haraka/haraka-plugin-geoip#50
Where is the code for the lite version of this package? It seems to be outdated even though it's pushed to npm under the most recent version of the non-lite package.
The text was updated successfully, but these errors were encountered: