[Bug 175605] Review Request: perl-IO-Multiplex

[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 report.

Summary: Review Request: perl-IO-Multiplex


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





------- Additional Comments From lmb at biosci.ki.se  2005-12-20 05:18 EST -------
Is there any policy for splitting perl packages into subpackages? I see in the
http://fedoraproject.org/wiki/PackageNamingGuidelines that splitting a CPAN
module is a viable option. But how important is dependency granularity?

Check this: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174099

So far nothing in FE has been borked by this. That also means that nothing else
in FE is depending on perl-IO-Multiplex. So my opinion is that a subpackage is
in order in this case. But I'm ready to be convinced otherwise...

ie:
perl-Net-Server
    ^
    |  (subpackage split)
    |
perl-Net-Server-Multiplex -> perl-IO-Multiplex

The alternative is to just add a Requires: perl-IO-Multiplex in perl-Net-Server.
Which alternative is preferable?

On a different note, who is maintaing postfix (in core)? And what would the
implications be for mucking with master.cf and main.cf? I would like to have
scriptlets in postfix-postgrey that modify those files to add funtionality. Much
the way as the kernel plays with grub.cong. But the modification of
smtpd_recipient_restrictions would be left as an excercise for root. ;-)

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