[Bug 476460] Review Request: pymilter - Python interface to sendmail milter API

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=476460





--- Comment #18 from Stuart D Gathman <stuart at gathman.org>  2009-02-01 22:40:23 EDT ---
The python-pydns is an optional dependency.  The dns module is often handy for
milters that need to lookup MX records, for callback, for instance - but is not
part of the core functionality.  Debian packages would have an optional
dependency.  In milter applications, missing optional packages result in
smoothly degraded function.  A user of pymilter, would get a package not found
exception if they tried to use Milter/dns.  I am torn, I really ought to put
the simplified wrapper for pydns (Milter/dns) in pydns - but was reluctant to
do so, wanting to minimize changes to pydns.  But now that I am the maintainer
of pydns, perhaps that is the best way.  Milters could also use dnspython - a
larger and more capable DNS library for python.  In fact, pyspf-2.1 can use
either library.

So how does Fedora handle optional packages?  Just add the dependency, and who
cares if a few extra K for pydns is pulled in?  I have a feeling it is either
that or move the Milter/dns module to pydns.  However, that does not solve the
larger problem of optional or alternate libraries - which can crop up in any
potentially dynamically linked language, including C.

%python_sitelib  - I am not clear when to use python-sitelib vs python-archlib.
 I am hearing however that the policy is to remove all unused macros - and
resurrect them from CVS if needed.

I will fix that and the other issues, and will think about whether to remove
Milter/dns or just add the dependency.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.