a8ed60296a
If --fromgit=<url> is specified: - Shallow-clone the repo. - Export the tree from the clone. - Run .cdbrelease.lua hook in the root of the tree. - Merge any data returned into config. .cdbrelease.lua can do more-or-less whatever lua allows (e.g. using dofile, filesystem access, etc.) to figure out the settings it wants to provide. This allows it to do things like include files from mods for shared versioning logic and perform more complex version number calculations, like NodeCore does. It could also be a security risk, so this should be used only on repos that the user has good control over. The canonical example is for .cdbrelease.lua to compute its own version number from stats that get baked into the file by the export step based on .gitattributes. Things like defaulting the pacakge name and author are possible too. Settings that are already explicitly specified at an earlier step are ignored from .cdbrelease.lua.
========================================================================
Prerequisites:
- You must have an existing account on content.minetest.net, and must
have a password configured (i.e. you can't use GitHub login for this).
- You must have already setup your package; this script will not create
new packages for you.
- Your package must use VCS for release, and have the source repo URL
already registered; file upload is not supported here.
........................................................................
To install the script:
- Have nodejs (and npm if packaged separately) installed.
- Clone/download the project.
- Run "npm i" in the project dir to install dependencies.
........................................................................
To create a release:
- You need to decide on a unique title for the release.
- In this project's dir, run:
node . --user="yourname" --pass="yourpass" --pkg="yourpackage" \
--version="new-version-title"
- You can also set optional parameters:
--branch="..." to set the VCS source branch, if not master.
--min="..." to set the minimum Minetest version.
--max="..." to set the maximum Minetest version.
- If a release with a matching name is detected then the release will
be aborted. Don't rely on this too much, as it may be fragile, e.g.
not work if a release exists but is pending approval.
- No news is good news. If you don't see anything then it probably
worked. Check on content.minetest.net to be certain.
========================================================================