-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Magnus,
Magnus Holmgren wrote:
> Given the overall quality of the libspf2 command-line utilities - lack
> of manpages (which I'm working to rectify, though), no support for HELO
> checks, override and fallback unimplemented, etc - I wouldn't mind if
> spfquery.mail-spf-query-perl were given a higher priority than
> spfquery.libspf2, even if the latter should execute faster. I think the
> same goes for spfd.
>
> What discussions did you have with the previous libspf2 maintainer? I
> can see how there can be confusion if at some point in the futures the
> relative priorities were to revert back.
I am maintaining libmail-spf-query-perl (AKA Mail::SPF::Query) within the
Debian Perl Group. Mail::SPF::Query (M:S:Q) has been superceded by
Mail::SPF[1] (M:S, written by me), but there's still a lot of Perl
software that uses M:S:Q, so we cannot drop it (yet). I haven't managed
to bring M:S (source: mail-spf-perl; binaries: libmail-spf-perl,
spf-tools-perl) into the Debian Perl Group yet (I'm currently busy with
exam preparations), but I'm planning to do so soon. Then, the M:S
man-pages should have the highest alternatives priority over both M:S:Q
and libspf2, as M:S has the most advanced spfquery and spfd tools and the
most complete man-pages for them.
I have added alternatives support to all of M:S, M:S:Q, and libspf2 (I was
the one who submitted the patch). This is the order I originally
envisioned:
Mail::SPF 100
libspf2 75
Mail::SPF::Query 50
But I can very well see changing libspf2's alternatives priority to 25
until it ships better man-pages. It's up to you.
> Another thing: will you add a Conflicts: spfquery (<= 1.2.5-4) on the
> next upload?
Yes.
Julian.
References:
1. http://search.cpan.org/dist/Mail-SPF/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFGCSjfwL7PKlBZWjsRAoS6AJ9KU0qe98eIn27Dh3h/ZvqWamhi1ACg76v9
1JCJulrA3+17LRuxkOL+eVg=
=tfwr
-----END PGP SIGNATURE-----
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007
Hash: SHA1
Magnus,
Magnus Holmgren wrote:
> Given the overall quality of the libspf2 command-line utilities - lack
> of manpages (which I'm working to rectify, though), no support for HELO
> checks, override and fallback unimplemented, etc - I wouldn't mind if
> spfquery.mail-spf-query-perl were given a higher priority than
> spfquery.libspf2, even if the latter should execute faster. I think the
> same goes for spfd.
>
> What discussions did you have with the previous libspf2 maintainer? I
> can see how there can be confusion if at some point in the futures the
> relative priorities were to revert back.
I am maintaining libmail-spf-query-perl (AKA Mail::SPF::Query) within the
Debian Perl Group. Mail::SPF::Query (M:S:Q) has been superceded by
Mail::SPF[1] (M:S, written by me), but there's still a lot of Perl
software that uses M:S:Q, so we cannot drop it (yet). I haven't managed
to bring M:S (source: mail-spf-perl; binaries: libmail-spf-perl,
spf-tools-perl) into the Debian Perl Group yet (I'm currently busy with
exam preparations), but I'm planning to do so soon. Then, the M:S
man-pages should have the highest alternatives priority over both M:S:Q
and libspf2, as M:S has the most advanced spfquery and spfd tools and the
most complete man-pages for them.
I have added alternatives support to all of M:S, M:S:Q, and libspf2 (I was
the one who submitted the patch). This is the order I originally
envisioned:
Mail::SPF 100
libspf2 75
Mail::SPF::Query 50
But I can very well see changing libspf2's alternatives priority to 25
until it ships better man-pages. It's up to you.
> Another thing: will you add a Conflicts: spfquery (<= 1.2.5-4) on the
> next upload?
Yes.
Julian.
References:
1. http://search.cpan.org/dist/Mail-SPF/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFGCSjfwL7PKlBZWjsRAoS6AJ9KU0qe98eIn27Dh3h/ZvqWamhi1ACg76v9
1JCJulrA3+17LRuxkOL+eVg=
=tfwr
-----END PGP SIGNATURE-----
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007