Item13169: PERLDEPENDENCYREPORT is not reporting extension dependencies.

It appears to generate the Core dependency report twice.

---

Hijacking this task for a 2nd issue with similar symptoms. On a "tarball" style installation, it generates an empty report. The issue is that we don't ship the DEPENDENCIES files for extensions, so this feature is useless except in a pseudo-installed system.

The only source for dependency information in a Foswiki release for extensions is embedded in the [extension]_installer files, which we also do not ship for default extensions.

-- GeorgeClark - 08 Feb 2015

The fix is simple enough. Add the DEPENDENCIES file to the MANIFEST. BuildContrib appears to do the right thing, and it restores the dependencies report for extensions. So the question becomes, do we want to do this? If we do, then build.pl manifest target should include DEPENDENCIES, and we might want to flag a warning for extensions that are built without including the DEPENDENCIES file.

Crawford, any thoughs?

-- GeorgeClark - 08 Feb 2015

Yes, adding DEPENDENCIES makes a lot of sense.

-- MichaelDaum - 09 Feb 2015

Sounds fine.

-- CrawfordCurrie - 15 Feb 2015

Commenting is disabled while not logged in