I added the constant and did a program to update. It is on the dev branch of bgrabitmap.
In BGRABitmapTypes there is constant
BGRABitmapVersion and function
BGRABitmapVersionStr which formats it.
const
BGRABitmapVersion = 9090300; // that means 9.09.03.00
function BGRABitmapVersionStr: string; // which returns 9.9.3
Releaser programThis program update the version of any library. It works with an input file (that I called a logic file) that specifies where version numbers are.
It will create the JSON file if it does not exist but is mentionned in the logic file.
The program is in
dev/releaser and can be used as a command line.
https://github.com/bgrabitmap/bgrabitmap/tree/dev-bgrabitmap/dev/releaserHere is the file
bgrabitmap.logic for BGRABitmap:
cd ..\..
manager update_BGRABitmap.json
archive https://github.com/bgrabitmap/bgrabitmap/archive/v$(Version).zip
cd bgrabitmap
package bgrabitmappack.lpk
package bgrabitmappack4fpgui.lpk
package bgrabitmappack4nogui.lpk
const bgrabitmaptypes.pas BGRABitmapVersion
@lainz
If I understand, you use the same url for the zip file.
I suppose you're wondering if the transfer would be interrupted. That's a good question.
Alos I guess that could lead to following:
- package manager downloads the JSON
- you release a new version
- package manager downloads the new version but stores that the version number is older
Not sure if it matters