Item9644: Pass the Foswiki RELEASE & VERSION strings on to Extensions repository in configure when using install & update

As discussed on IRC today with MichaelTempest. Easy task, but needs to be a ReleaseBlocker.

We'll be kicking ourselves next year if 1.1 is still using the same FastReport topic as Foswiki 1.0.

We need at least the possibility of being able to show only relevant/compatible plugins from configure installer appropriate for the Foswiki version making the request.

• Copy FastReport to FastReport01x10
• Update the configure code to go there for the query

Then we can worry about fixing FastReport at our end (later).

-- PaulHarvey - 08 Sep 2010

So who is fixing this?

-- KennethLavrsen - 11 Sep 2010

can we do this a tiny bit differently?

1. add another URL params major=1;minor=0;patch=0;build=4574
2. change the FastReports topic to use INCLUDEs based on thoseparam (and obviously default to 1.0.....

that way we have a way of tracking what versions are out there and using configure, and don't leave ourselves needing to revisit this again?

this would mean the only thing we have to do now is to add the urlparams to configure, and then when we finally need the report updated, we're already sending the required info....

-- SvenDowideit - 13 Sep 2010

I am out of the office until Thursday. I think Sven's suggestion is reasonable. I'll see if I can get some time tonight.

-- PaulHarvey - 13 Sep 2010

I didn't see any built-in way to extract major/minor/patch/build as separate discrete entities; I think that's beyond the scope of this task (but certainly a worthwhile endeavour. We need to improve our version/dep management).

So I just passed along Foswiki.pm's VERSION and RELEASE strings to FastReport as version and release query params.

And at GeorgeClark's suggestion, PLUGINSAPIVERSION.

-- PaulHarvey - 13 Sep 2010

Commenting is disabled while not logged in