#28865: p5-libwww-perl: new version 6.02, which is now in multiple modules distributed separately ------------------------------+--------------------------------------------- Reporter: l2g@… | Owner: l2g@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: p5-libwww-perl ------------------------------+--------------------------------------------- Comment(by l2g@…): The above was meant to say "LWP-Protocol-https," not "LWP-UserAgent- https." It looks like Gisle Aas (the author) wanted to break a circular dependency or avoid some other kind of dependency hell. So LWP::Protocol::https got its own package. Thus, anything needing HTTPS support in LWP should declare dependencies on both LWP and LWP::Protocol::https, and packages that don't need HTTPS don't have to have the extra modules installed. Now, I'd rather not have to go through all 59 ports depending on LWP to find out whether or not they require HTTPS, or else it'll be a long time before this upgrade gets done. So my idea is to make an "ssl" variant in this port, and make +ssl the default. Benefits: (1) We keep HTTPS support enabled in the upgrade, following the Principle of Least Astonishment. (2) We allow those who don't want the extra HTTPS modules to disable the variant and uninstall those ports. In the long term, it would be nicer to go back and audit those p5-libwww- perl dependents, have all those that need HTTPS depend on p5-lwp-protocol- https, then only after all that's done, remove the p5-lwp-protocol-https dependency from p5-libwww-perl. Phew. That's a mouthful. Any objections or concerns? -- Ticket URL: <https://trac.macports.org/ticket/28865#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS