On our Ubuntu 16.04.1 LTS, after installing mod_perl (simply out-of-the-box with apt-get), CGI.pm installs:
We have 20+ Ubuntu LTS instances running on Google Cloud Platform, 12.04, 14.04 and 16.04, on all mod_perl and CGI.pm run fine.
Only non-issue – and only on stopping/restarting service apache2 – are lines like these in the apache2 error.log:
[Sun Sep 11 08:31:00.430150 2016] [mpm_prefork:notice] [pid 15239] AH00169: caught SIGTERM, shutting down
[ error] oh jeez, server dumped core
[ error] oh crap, server dumped core
On Sat, Sep 10, 2016 at 6:18 AM, Igor Chudov <firstname.lastname@example.org> wrote:I can, and will of course, install CGI myself as all my sites use it and I have 84,000 lines written using it.My concern is that it will break at some point going forward if it is not maintained.Out of curiosity, why do you think that it's not maintained ?It's just excluded from perl distribution and it's ok as it doesn't support modern stuff like HTML 5, AJAX, HTTP/2, etc.I try to use CGI.pm in ways that are not questionable, such as using it in object oriented manner without importing its functions into my main namespace.Going forward, I think, I should get the message and switch to something new that will be maintained -- but to what?If you don't plan to re-design your websites I'd recommend keep CGI.pm.It's maintained, just not part of perl itself now ( DBI.pm isn't as well and what?).Just consider CGI as one of CPAN modules (as well as alternatives you can find).--Regards,Misha