Item13117: Config.spec files built for Foswiki 1.1 do not work on Foswiki 1.2
Priority: Urgent
Current State: Closed
Released In: n/a
Target Release:
Applies To: Extension
Component: Configure
Branches: master
Catch-all task to check in spec file updates that are exposed by new configure code.
--
GeorgeClark - 27 Nov 2014
Any plugins updated here need to be released before 1.2 is released.
--
GeorgeClark - 27 Nov 2014
Bumping this to urgent. Many or most 1.1 era Config.spec files have issues. We really need to be more backwards compatible.
- Mandatory config items flagged with "M" crash configure. Have to edit from file system to get by.
- All config items are now assumed mandatory. Need to add CHECK="emptyok" to get equivalent non-mandatory items.
--
GeorgeClark - 14 Jan 2015
I think the fix is to bring back the "M" option, and have it set/clear the CHECK= options if CHECK= is missing. And maybe generate a warning that
M
is obsolete. But only if we are going to re-release a lot of old extensions.
No... we need to invert the default. Otherwise it will be a real mess. 1.1 can't default to emptyok and 1.2 default to mandatory.
- change CHECK= option from "emptyok" to "notempty" (equivalent of Mandatory, something must be entered)
- Bring back "M" option as legacy, and have it set the CHECK="notempty" option.
--
GeorgeClark - 14 Jan 2015
Closed. Things seem to be working now. This task can be re-opened if more compatibility issues are found.
--
GeorgeClark - 15 Jan 2015