Extensions - Add some official "legacy" extensions as "sideloaded" submodules to assit merges and preserve our changes
Draise14 opened this issue · comments
The new bfa_default_addons addon we have for pre-downloaded extensions is now available as individual repositories... which might make it easy to "update" when we do a sub-module update.
For this particular case, we have about 4 addons that have some of our changes now included as core addons. To make sure they get updates I propose this:
- Add the 4 extensions to
//scripts/addons_contrib - When doing a merge, update submodules
- Compare these 4 extensions to the 4 core addons manually
Bit of a small overhead, but should be nice and easy to maintain this way - preserving our #BFA changes.
OR.. add forks of these addons to the Bforartists repository somehow then add those as sub-modules to the repo. One way or another, one addon module has to be compared and the changes merged in. Fortunately it's mostly only in 4 counted addons.
Note The core addons contain former legacy addon names, but code from the extensions. For some silly reason Blender renamed all their extensions to not be compatible with legacy overwrites and settings.
[CHANGES FROM BFORARTISTS]
io_mesh_stl\ = stl_format_legacy\
io_scene_3ds\ = autodesk_3ds_format\
space_view3d_copy_attributes\ = copy_attributes_menu\
space_view3d_pie_menus\ = viewport_pie_menus\
Hope I did it right.