#5924 - Fix imports/addons behaviour
| Identifier | #5924 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Fix imports/addons behaviour |
| Status | Closed (rejected) |
| Tags |
Roadmap: v11 (custom) |
| Handling member | Deleted |
| Addon | core_upgrader |
| Description | The current behaviour of imports/addons is that files are packaged into the archive. But the archive itself is not updated exactly to the contents of the addon. This means it could have alien files in the archive and thus causing an inaccurate hash for upgrade checking (for non-bundled addons) (although there is a secondary file m time check that helps reduce false positives).
We might not want to sync them though. The upgrader packs old files for potential re-installation. So maybe a better solution is to instead use exports/addons, or to generate new TARs with the suffix name.original.tar to indicate those TARs contain the exact file repository of an addon. Discuss ideas. This will be necessary before v11 is released for proper addon upgrading. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments