Replies: 1 comment
-
The data files are mostly identical, with the exception of the For instance, 060 support only exists in v7, some chipset emulation options have been changed, and Fast Copper doesn't exist, to name but a few. The two applications create separate directories under $HOME by default and install their files in separate system dirs as well, so they can co-exist on the same system without issues. |
Beta Was this translation helpful? Give feedback.
-
We provide Amiberry v5 packages from our APT repository, and I am wondering how to best migrate users, where upgrades are pulled via
apt upgrade
. As far as I understood, Amiberry-Lite is a closer replacement for smaller ARM and RISC-V systems, while Amiberry v7 would be probably better an optional offer. But to achieve that, we'd need to provide Amiberry-Lite asamiberry
package, and Amiberry v7 hence with a different name. Long-term this however would not be great, but I want to ship Amiberry v7 asamiberry
, and Amiberry-Lite asamiberry-lite
.Is it possible to somewhat clone the Amiberry v7 data/configs to Amiberry-Lite without issues? We will implement a separate Amiberry-Lite installation and package. So users who run an APT upgrade will get and can test Amiberry v7. If it is too slow for their hardware, they can install Amiberry-Lite, and we could provide an automatic migration/clone of the config. The question is whether this works/is compatible.
An alternative would be to create a backup of the old config via
preinst
maintainer script, so it does not get migrated to Amiberry v7, but instead is picked up by the Amiberry-Lite package, in case it is installed.Any idea how to achieve this best would be great 🙂.
Beta Was this translation helpful? Give feedback.
All reactions