Brief summary of issue / Description of requested feature:
Additional (optional) informations which the package manager can then recognize and which are also gettable by
Lua see #4869
I think this could also be helpful for the mudlet-package-repo/manager
SlySven on Discord:
I once mooted exactly that in the past - we currently fire up a separate Lua interpreter just to parse the single mPackageName = xxxx Lua script in the config.lua file that goes into the root directory of an archive format file - I envisaged adding additional entries (and a form based UI during the package export process to ask) for:
* Author
* License
* Comment/Notes/Description (?)
* Some sort of version number (possibly with auto-increment when resaved?)
* Last save/update date - bearing in mind that synced modules get resaved when the profle does in some cases - this might be two entries
* Dependencies (?)
I also wanted this same data to be writting into the zip comment so that some archive file handling tools could show this - for *nix users this would show up on the command line if the archive was listed/tested or under some other situations
Extra information, such as Mudlet version, operating system and ideas for how to solve / implement:
I think useful informations could for example be: package name, author, package version, creation date etc.
The mudlet package manager could then use this information to compare them with the package repo and check if there is a new version of the package (for example)
Brief summary of issue / Description of requested feature:
Additional (optional) informations which the package manager can then recognize and which are also gettable by
Lua see #4869
I think this could also be helpful for the mudlet-package-repo/manager
SlySven on Discord:
Extra information, such as Mudlet version, operating system and ideas for how to solve / implement:
I think useful informations could for example be: package name, author, package version, creation date etc.
The mudlet package manager could then use this information to compare them with the package repo and check if there is a new version of the package (for example)