How can the author/maintainer update this information?
The latest stable version of FPC/Lazarus is automatically added + Lazarus Trunk.
Tell you when an update is requested?
Only in special cases, when a package does not support Laz version x or FPC version y.
But there is also the case that a package is submitted some time ago when - say - Laz 2.0.12/FPC 3.2.0 were up-to-date, and was not changed since because it is considered complete by the author and also is not affected by the changes in Laz/FPC. How is the version information in OPM updated then? I guess it is not updated at all as I'd conclude from the example of the ColorPalette package which is marked to be tested up to Laz 2.0.2/FPC 3.0.4 although I just checked to see it working with current Laz trunk/FPC 3.2.2.
[EDIT]
I checked all packages that I maintain whether they work with the current release version, Laz 2.2.4/FPC 3.2.2, and I found that their demo/test projects work fine on Win-64bit; the only one which crashes is the TParadoxDataset package which works on Win-32bit though. I did not test other widgetsets.
Here's a list of all these packages:
- calite
- captcha
- chemtext
- colorpalette
- extrasyn
- fpspreadsheet
- gridprinter
- industrial
- jvcllaz
- lazbarcodes
- lazmapviewer
- mbcolorlib
- spktoolbar
- tparadoxdataset -- 32 bit only!!!
- tvplanit
Please update the OPM record of tested versions for these packages. (BTW, usually it is marked that packages work with versions as old as Laz 2.0/FPC3.0 - I doubt that is information is valid)
During the test I noticed that the
lazbarcodes package requires an update. Its zip file is here:
https://sourceforge.net/projects/lazarus-ccr/files/LazBarcodes/lazbarcodes-2.0.0.zip/downloadThere will be also an update for the
tvplanit package in a few days.