@"Tuybit" #p25348
Your plugin sounds interesting—could you share a bit more about it?
Did you intend to only create an installer for yourself ?
I haven't tried to create an installer for mine, because I assumed it would be integrated into the main fork.
From what I have been told, the dev team is considering a new repository for plugins.
Regarding:
"If I wanted to distribute, I just share my folder for others to compile, even though it doesn't sound good."
At the very least, you could keep your main/master/deploy branch (or whatever it ends up being called) updated. Personally, I’d rebase my changes and keep my mods on top of the latest application state, especially for an unofficial fork like this. It would be very easy for everyone to see what your code delta is, e.g. 5 commits ahead.
Say, I come across your repo and see it’s 5 commits ahead, I’d simply pull it and follow the instructions you have left in the documentation (e.g., running a setup.py or deploy.py script). If there is nothing extra, just point to the original build script or instructions.
That approach seems manageable.
Also in the readme.md you can leave a deploy ready command for linux or windows like:
git pull {your repo name}
{prebuild setup or whaterver.. maybe some pip install something}
python {build script or command}
{postbuild cleanup or whaterver}
Say what prerequisites we should have, i.e. git, python and pip. The pipeline is done.
