Item12855: Audit core DEPENDENCIES
Current State: Closed
Released In: 2.0.0
Target Release: major
Applies To: Engine
There are dependencies in lib/Foswiki/contrib/core/DEPENDENCIES that are not. Audit to make sure all dependencies really are. Marked as Urgent to ensure this gets done before release.
- Win32::Console - was (may still be?) a requirements for generating language files on Windows. Should not be a core dependency.
- 12 Apr 2014
It's conditionally "required" as a dependency of
. I've no idea how it's actually used.
- 12 Apr 2014
Found a couple of errors in our SystemRequirement
document: CPAN packages File::Copy::Recursive and JSON are not listed.
- 30 Nov 2014
There's some question about which dependencies we should include. The attached script hack.pl, when run from the lib directory, does a scan for explicit dependencies.
This list may not be complete, but I suspect it's a lot better than the one we're using. Yes, I tried scandeps, and it was awful.
- 15 Jan 2015
I see two reasons for inclusion in DEPENDENCIES
- Make sure the module is installed .. The obvious one.
- Report the version installed, and where it was found in lib path in the PERLDEPENDENCYREPORT
To me the latter is in some ways more important, even for plugins that include their own dep's in
. When something is not working, it can be pretty valuable to be able to report which versions of perl modules are installed, and where they were found, from the context of the web server or fcgi process. So there is some value to even listing core modules in DEPENDENCIES.
- 16 Jan 2015
We also need to remove the dependencies on the PatchItem12225Contrib
for any extensions that have converted to decimal version strings.
- 01 Mar 2015
I think that this can be closed. The note about reporting versions of loaded modules was addressed in another task. FoswikiServerInformation
has a list of all loaded modules with their versions and file locations.
- 05 May 2015