Add-On Repository #56165

New Issue

Campbell Barton · 2018-07-31T04:49:30+02:00

Campbell Barton commented

2018-07-31 04:49:30 +02:00

Motivation:

Support updating add-ons from within Blender.

Add-ons can currently be downloaded an installed, but there is no good way to update them.

Description:

While package management is a big topic. We should investigate having an add-on repository.

This functionality can it's self be an add-on, we should test such functionality carefully, since there is quite some scope for mis-use (users need to put complete trust in the author) on the other hand, this is already the case when downloading an add-on from the internet.

Examples of Application-Level Package Managers

Open Topics

Expand the scope of this project?

Even if this isn't done initially, it could be allowed for in the design.
- Application templates.
- Themes.
- Key-maps.
- HDRI images, matcaps (overlaps with asset-manager).

**Motivation:** Support updating add-ons from within Blender. Add-ons can currently be downloaded an installed, but there is no good way to update them. **Description:** While package management is a big topic. We should investigate having an add-on repository. This functionality can it's self be an add-on, we should test such functionality carefully, since there is quite some scope for mis-use *(users need to put complete trust in the author)* on the other hand, this is already the case when downloading an add-on from the internet. **Examples of Application-Level Package Managers** - [Atom Packages ](https://atom.io/packages) - [Emacs (Melpa) ](https://melpa.org) - [Vim-plug ](https://github.com/junegunn/vim-plug) **Open Topics** - Expand the scope of this project? *Even if this isn't done initially, it could be allowed for in the design.* - Application templates. - Themes. - Key-maps. - HDRI images, matcaps *(overlaps with asset-manager).*

Campbell Barton self-assigned this 2018-07-31 04:49:30 +02:00

Campbell Barton commented

2018-07-31 04:49:30 +02:00

Added subscribers: @ideasman42, @dfelinto, @mont29, @Sergey, @brecht

blender-admin commented

2018-07-31 04:49:30 +02:00

blender/blender-addons#68976 was marked as duplicate of this issue

Campbell Barton commented

2019-09-02 05:23:36 +02:00

Added subscribers: @johnsyed, @nokipaike

Campbell Barton changed title from ~~Minimal Python Add-On updater~~ to Add-On Repository

2019-09-02 05:24:49 +02:00

Andy Cuccaro commented

2019-09-04 23:00:21 +02:00

Added subscriber: @AndyCuccaro

AR commented

2019-12-02 18:15:08 +01:00

Added subscriber: @arc4g-1

Dave Keeshan commented

2020-04-13 18:31:47 +02:00

Added subscriber: @mavek

Dave Keeshan commented

2020-04-17 15:16:50 +02:00

This problem feels like it has been solved already and has an available solution. PYPI. There even have all the code up and available:

PyPI Warehouse

They are storing version controlled, python files, is that not exactly what a big bunch of blender addons look like too.

It might be easier to look at what the pypi warehouse can do and remove functionality. Change the user authorisation to blender ID. If edits made are sensitive, it should be possible to maintain a soft fork of pypi that would allow future edits upstream be merged in down stream. The biggest question would be where would the repo be hosted and who would maintain it.

They call pypi their cheeseshop, and people get their wheels, of cheese.

Looking at extending the suzanne model, operation. What do monkeys like, bananas. So an addon is a banana, and they are all stored in the banana-tree. Call it all NANA for short, or BANA (Blender Addon Nest Assets)

This problem feels like it has been solved already and has an available solution. PYPI. There even have all the code up and available: [PyPI Warehouse ](https://github.com/pypa/warehouse) They are storing version controlled, python files, is that not exactly what a big bunch of blender addons look like too. It might be easier to look at what the pypi warehouse can do and remove functionality. Change the user authorisation to blender ID. If edits made are sensitive, it should be possible to maintain a soft fork of pypi that would allow future edits upstream be merged in down stream. The biggest question would be where would the repo be hosted and who would maintain it. They call pypi their cheeseshop, and people get their wheels, of cheese. Looking at extending the suzanne model, operation. What do monkeys like, bananas. So an addon is a banana, and they are all stored in the banana-tree. Call it all NANA for short, or BANA (Blender Addon Nest Assets)

xan2622 commented

2020-04-27 18:29:05 +02:00

Added subscriber: @xan2622

Thanh Phan commented

2021-08-17 08:14:04 +02:00

Added subscriber: @thanhph111

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Add-On Repository #56165