On Sun, Sep 12, 2021 at 1:36 PM Christophe JAILLET <christophe.jail...@wanadoo.fr> wrote: > > Hi, >
Caveat: I don't know much of anything on this stuff > I've also been looking at this README file today and I have a few questions: > - some of the explicitly named modules looks redundant with what is > already in Bundle::ApacheTest > - Crypt::SSLeay looks spurious. It doesn't compile on my machine > because of function name conflicts with my openssl > there is also a big warning that says that (recent) > LWP::Protocol::https should be enough Seems consistent with this rev: $ svn log -c r1237461 ------------------------------------------------------------------------ r1237461 | rjung | 2012-01-29 15:39:23 -0500 (Sun, 29 Jan 2012) | 14 lines Add LWP::Protocol::https to Bundle::ApacheTest and update version number of the bundle. Otherwise https support will not be installed. The docs of the added module tell us: "This module used to be bundled with the libwww-perl, but it was unbundled in v6.02 in order to be able to declare its dependencies properly for the CPAN tool-chain. Applications that need https support can just declare their dependency on LWP::Protocol::https and will no longer need to know what underlying modules to install." I guess the way we run it we can just casually change it in SVN and not worry about a release? > - this list is not in line with what is configured in .travis.yml >From eyeballing they don't seem too far off > What puzzles me the most is the 3rd point. Unfortunately I spoiled my env a little after reporting my results by playing with the cpanm one-liner, so when I just went in to remove Crypt::SSLeay I actually got more successful tests than what I reported for 2.4.49. I think we could synch them up, using the more modern list in travis as a basis, and cross-link them with comments so they have a chance of not drifting much further
