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-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 ------- Additional Comments From mpeters@xxxxxxx 2005-11-10 13:47 EST ------- I'm going to contact my service provider and ask why access isn't working for some people. -=- With respect to splitting it - I can do that, but then perl-Readonly-XS will need to Require perl-Require because it is useless without perl-Readonly. However - perl-Readonly should also require perl-Readonly-XS because it gives perl-Readonly-XS a performance boost, and perl scripts that use perl-Readonly will not require perl-Readonly-XS by automatic dep resolution, so the only way to get perl-Readonly-XS pulled in with yum is to have perl-Readonly require it. Since the two modules will thus need to require each other, and are maintained by the same maintainer, and released in pair (new version of one means new version of other) - does it really make sense for them to be separate packages in this case? -- 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.
