Item8898: BuildContrib and the core release builder need to generate canonical DEPENDENCIES and MANIFEST files
Current State: Confirmed
Released In: n/a
Target Release: n/a
file shipped with Foswiki is not really useful to the site admins. It's a set of include statements for files that are not provided. These are includes of directories that were used for packaging the release and are not shipped. The 1.0.9 MANIFEST file is shown below - none of these are of any use to a site admin that I can see.
A MANIFEST file, if shipped with Foswiki, should consist of the actual shipped file names, along with their attributes and descriptions.
- 13 Apr 2010
And any relative reference in a MANIFEST file should be relative to something sensible - either the file itself (which I think is preferred) or the root. But not SVN, which clearly isn't shipped!
- 23 Jul 2011
I need this to simplify building separated packages - at minimum the core MANIFEST, which resides in
So I'm going to make it so for 1.1.5 and
, and then we can think about the core extensions (which we could achieve by just making the build doit)
- 28 Jan 2012
George would like something different from what I need - a complete list of files that should go into the zipfile. This needs to be generated by BuildContrib
when it processes the lib/MANIFEST. Similarly the a generated DEPENDENCIES file should be shipped in the release.
- 31 Jan 2012
Back to the original issue on this, lib/MANIFEST is of no value, and probably should just be omitted from the shipped packages.
- 12 Jan 2015