Autoupdate addons from repo and blender updates
What about some solution like pip in Python or Visual Studio Code? Eg. starting Blender and checkig updates for Blender or addons. Exist new version, the blender updates addons or modules in blender from repo. Blender can have something like repository.blender.org the any author registerig the source of files, and informing about new version, changes by right .md file.
In the simple way can be new parameter in addon, where to check version:
"repo_url": " github.com/rlguy/Blender-FLIP-Fluids/ "
"repo_version": " github.com/rlguy/Blender-FLIP-Fluids/blob/master/__init__.py "
7 Comments
A final, singular, PRE-INSTALLED & OFFICIAL, Add-on Manager to rule them all
Blender should not care where is hosted just offer the link to the repo, eg. github, gitlba, FTP, or SVN and GIT dir as ftp views. Blneder should offr just regist these repos in on database to check where was last update on repo and compare versions. This same whole blender can be on github as release to update, the philosophy is open for any opensource like blender.
This has been proposed numerous times. Each time the discussion is always the same- who is hosting the addons, who is paying for the hosting, what about paid addons, this makes more sense as a third party solution, why doesn't blendermarket do it, etc etc etc. Search for the topic and read some of those old discussions
* @testure * Blender should not care where is hosted just offer the link to the repo, eg. github, gitlab, FTP, or SVN and GIT dir as ftp views. Blneder should offer just regist/add these repos in on database to check where was last update on repo and compare versions. This same whole blender can be on github as release to update, the philosophy is open for any opensource like blender. Worst is for licensed, then license manager should allow to update or not..
* @ManBlender * right, and where is that database? does it ship with Blender? what about addons that come out after a Blender release? my point is, you're making this sound like a "duh of course we should have this feature" when it has been suggested millions of times and dismissed each time.
* @testure * It's detail? That is sense of this feature where db has info that this addon working with this version of blender or not. Ok... You convicing me.. I'll do this for my own addon with private db, and planing do money for this.. f**k open source :D
* @ManBlender * I think, that can be local sqlite too (or files with manifest?), and plugins can have some version.json or manfiest.json code.visualstudio.com/api/references/extension-manifest The most easy way can be parameter in addon about the main.py file where is BL_info:
bl_info = { "name": "New Object", "author": "Your Name Here", "version": (1, 0), "blender": (2, 80, 0), "location": "View3D > Add > Mesh > New Object", "description": "Adds a new Mesh Object", "warning": "", "doc_url": "", "category": "Add Mesh", "repo": " github.com/rlguy/Blender-FLIP-Fluids " "repo_bl_info": " github.com/rlguy/Blender-FLIP-Fluids/blob/master/__init__.py " //sugestion to use small files }
Then blender checking bl_info with actual file that blender have and with remote on repo - as version. It be good some .md of changes to display this for new.