Item3932: there needs to be a machine readable & testable DEPENDANCY list in a contrib package

the installers presume that the only thing they are for is to install. so there is no way to ask for a list of dependancies.

similarly, the TWiki:/Plugins need to list dependancies in the TWikiForm - so that configure (via FastReport can test for, install and otherwise inform the user.

I'm wanting it to do dependancies for the debian plugin packages - right now thats really messy.

similarly, FastReport should actually be able to find a package url from the contrib topic, rather than the URL being manufactured by hope and tradition.

Also, need to know is there is a compuloryly manual post install step, or if (in the rare cases the installer really must be run)

mmm, need author and license too really

-- TWiki:Main/SvenDowideit - 22 Apr 2007

Several times I have debated the merits of moving the DEPENDENCIES list into a separate file outside the installer script itself. To do this would simply involve shipping the existing DEPENDENCIES automatically in the extension directory. Would that answer for you?

-- TWiki:Main.CrawfordCurrie - 23 Apr 2007

the other option, is to add parameters to the installer scripts like --show_dependancies, --show_manifest and --show_version

and if we implement it so that the part after show_ is used as the key into a hash, we can even add more infos later.

if we then add those key'd info's to the uploaded topic, we can mine it form FastReports - as in, add META:PREFERENCE

-- TWiki:Main.SvenDowideit - 23 Apr 2007

That's a better idea.

Reclassifying as enhancement.

-- TWiki:Main.CrawfordCurrie - 24 Apr 2007

I closed this some time ago; not sure why it is still open. I added the parameters to the installer scripts.

-- CrawfordCurrie - 13 Nov 2008 - 08:55