* Josh Kelley via RT (bug-Mail-Box@rt.cpan.org) [070911 03:09]:
Show quoted text>
> Queue: Mail-Box
> Ticket <URL:
http://rt.cpan.org/Ticket/Display.html?id=29266 >
>
> I'm sorry; by "RPM builder", I'm not sure if you mean the set of build
> scripts provided with RPM (which attempt to automatically handle
> dependencies and prerequisites and are confused by Mail::Box::Construct)
> or the person responsible for packaging Mail::Box into an RPM package
> (who can add a workaround for RPM's build scripts being confused by
> Mail::Box::Construct). I think you mean the latter, but I just wanted
> to clarify...
Yes, the latter.
Although I can understand why there are problems: Perl's ideas about
versioning is flawed. Probably, the best thing is to ignore information
from packages when filename != packagename.
Show quoted text> I've noticed that SpamAssassin, for example, uses two package statements
> in a row in situations like this, and the article I linked to seems to
> recommend it, and I think that RPM packagers generally prefer to see
> problems handled upstream where possible rather than at the packaging
> level. But if you would prefer that this be handled at the packaging
> level, I'll be happy to report it to the packager. Thank you for your time.
Yeh, that is the only correct thing: module authors (like me) are not
really willing to make changes to facilitate rpm... and deb, yum, etc etc
--
Regards,
MarkOv
------------------------------------------------------------------------
Mark Overmeer MSc MARKOV Solutions
Mark@Overmeer.net solutions@overmeer.net
http://Mark.Overmeer.net http://solutions.overmeer.net