Trying out the latest build and I layered in a few apps that are not viable as flatpaks or any of the other “preferred” methods and they did not survive the deployment of a new image. Perhaps I misunderstood the images listed at boot time. Can someone please clarify this?
That’s exactly how it’s supposed to be — Works As Designed™.
The main system is immutable, and only the approved/recommended overlays will be preserved just as you’d expect. Any other method won’t be compatible with the arkdep system.
1 Like
I’ve just updated Summit a minute ago and the sole layered package (fd) I have installed survived the “arkdep deploy command”. That’s what I understood from what @dennis1248 said in this post, the installed with layer should remain and those installed with pacman don’t:
How did you install the packages? If you pacman -Sy package it will be wiped on next update. If you arkdep layer package it will be automatically installed on any future updates.
The arkdep layer command is still fairly new and needs more testing. I suspect it can sometimes fail if the pacman cache is out of date and pacman refuses to refresh it, despite giving it a yy to force refresh. I still have to validate if this is indeed an issue and figure out how to circumvent it.
2 Likes
If any of the layered apps gave an error while updating, none of the layered apps will be installed in the new deployment. Fortunately will be solved in the next deployment.
May be that’s what happened to you?
Well I am back from my trip and will have some time to put it on my Framework 13 AMD laptop. The apps I layer in are: tailscale (which is a network service and should be part of the base image), ghostty (best terminal emulator - period, but flatpak version is not ready yet), darktable (to be able to access the AMD GPU for accelerated image processing), rocm-opencl-runtime (to provide said image processing acceleration) and rapid-photo-downloader (to ingest my photos properly). All other apps are installed via flatpak or Linux brew.