You should look at homebrew. It will allow package installs yet maintain immutability. Especially if you want to add things that don’t make sense in a container (like fastfetch, virtualization (qemu+libvirt), etc).
Thanks, I checked it out. But it is not a good fit for Manjaro Immutable.
Their own docs recommend you install it to your home dir, this is something you can do yourself already if you want to use Homebrew.
We will never touch the user’s home dir, if we ship Homebrew with the OS we’ll be stuck with it forever due to how these installed bins are made usable through a PATH override in the shell. If we pull it from the image this feature will break.
We also have now a test-manjaro-xfce image available, for those who love XFCE and a more classic desktop environment.
Tag added to topic.
Currently checking if I get COSMIC going as well …
Manjaro Rock - as simple as that. )
Manjaro Rocca (rocca means strengthened place in Italian) (according to a dictionary)
OK, I managed to get some COSMIC going. It can be installed via arkdep deploy test-manjaro-cosmic
.
To be able to install from flathub in the cosmic-store you have to open a terminal and issue: flatpak remote-add --user flathub https://flathub.org/repo/flathub.flatpakrepo
. Otherwise it will try to install via packagekit due to archlinux-appstream-data package.
I think the “Switch Image” Step very complex.
if Universal Blue only use this command will done
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable
I’d argue it is a lot easier, and a lot more user manageable in how it works right now as compared to rpm-ostree.
You only have to run this one single command to switch over the image.
sudo arkdep deploy test-manjaro-kde
But it will still default to test-manjaro-gnome
for updates using a plain sudo arkdep deploy
.
So you can either edit the config to tell Arkdep to pull another image as the default, or you can manually define test-manjaro-kde whenever updating.
In the stable release we intend to give you the option to select a desktop at install time. So you won’t have to perform a switch afterwards.
There are some solutions, but I do not really like any of them.
- Ship this info with the image and make Arkdep prefer it if this info is available, yet this will introduce vague functionality which is certain to cause confusion for users who will not understand why Arkdep is not respecting their configuration.
- Update the config when a specific variant is defined. Issue here would be that this is not atomic, if it messes up your config it can break your system.
- Have some type of wrapper script to perform non-atomic changes. But I dislike unnecessary abstraction, there shouldn’t be multiple paths towards the same goal.
on KVM(Virtmanager).
The installation was completed in English.
logi keyboard not work.
Logitech Wireless Keyboard K270
I gave up. I’m just waiting for the next ISO.
–
I tried again.
This time, the keyboard was recognized for some reason, so I was able to complete it.
I have add KDE. good.
I’m looking forward to the future.
I’d be happy if I could use Cinnamon as well.
Been following the thread since the testing release on the 3rd of August, but it has turned ‘rather quiet’.
Have there been any new news worthy developments on the work being done on Manjaro Immutable?
We are working on continuing to mature the technology, once it is mature enough we’ll attempt for a full proper release. I feel like the technology might almost be ready (but I have been saying this for 6 months already).
My current focus is to get an alpha/devel release out for public testing of Manjaro Gaming Edition with OpenGamepadUI. I am hoping to get it released by the end of this week.
You can follow the development of the immutable here; Immutable Launch · GitHub
And Gaming Edition OGUI here; Gaming Edition OGUI Alpha · GitHub
I use VMware BTW…
I couldn’t resist. My bad.
I find that Homebrew (for Linux) is greatly limited, in any case; due to it not supporting Casks – this makes it useful only for managing the most superficial of user applications.
I’d be hard pressed to see a need for it generally, let alone within this project.
A new ISO has been published and a new image has been made available for updating. The old ISO installer is no longer compatible with the latest image version.
This update contains minor changes and updates everything to the latest version of Arkdep.
Existing installs can be safely updated, but they will be missing some configuration causing it to “forget” certain settings. To prevent this, manually update migrate_files
in /arkdep/config
before updating.
migrate_files=('var/usrlocal' 'var/opt' 'var/srv' 'var/lib/AccountsService' 'var/lib/bluetooth' 'var/lib/NetworkManager' 'var/lib/arkane' 'var/lib/manjaro-branch' 'var/lib/power-profiles-daemon' 'var/db' 'etc/localtime' 'etc/locale.gen' 'etc/locale.conf' 'etc/NetworkManager/system-connections' 'etc/ssh')
For the actual release in the future such changes will be automated.
Afterwards you can simply update with;
sudo arkdep deploy
I currently use Project Bluefin which is based on Fedora Silverblue. In Bluefin, Homebrew in installed by default along with DistroBox + BoxBuddy. The Gnome Store only points to Flathub. So I can safely report that I have experience with installing software on atomic OS’s. The other day I installed DisplayCal from Flatpak to color calibrate my monitor. The Flatpak worked for the most part but was unable to install the profile due to the ArgyllCMS app not being installed with DisplayCal and not available on Flathub. Trying to run it on DistroBox bombed spectacularly (Fedora, debian and Arch distroboxes). Homebrew to the rescue! I could not install DisplayCal (it’s a Cask) but I could install Argyll-CMS and then I got rid of the error message plaguing me (only to be replaced with access denied due to immutability). Ultimately, I installed the profile and now enjoy a nice calibrated monitor.
Hunting down these types of deps which Flatpaks might expect on the native system we are actively hunting down, I can add argyllcms
to the package list if this is one such package.
I still consider myself a linux noob. I have installed ‘immutable’ to a SSD, no issues. This is my problem.
How do I open this file as root, /arkdep/config
?
“To make test-manjaro-kde
the default branch for future updates you will have to change repo_default_image
in /arkdep/config
. If left to test-manjaro-gnome
it would download the latest GNOME image when an update becomes available, even if you are currently running the KDE one.”
@Hipster I installed kate as an flatpak with the software center. Then i opened the config and changed it. Kate has all permissions, for some reason, which is wierd but ok.
Then open the terminal and type sudo arkdep deploy
and you’re good to go.
Keep one thing in mind though, this image is NOT uptodate. It is still on the 6.9 kernel, which is eol. After booting in the kde image you should open the terminal and type sudo usermod --add-subuids 100000-165535 --add-subgids 100000-165535 username
if you want to play with boxbuddy and some container stuff. username should be replaced with your username( ) or with
$(whoami)
, if you’re not quite sure.
Is that the best way to go? I mean that is one of these occasion arkdep-build should be for, i guess.
On the other hand the user can still add software with pacman to the install, at least as long as there is no new image. Should they do it? Probably not, but they can do it.
By the way the test-manjaro-kde image and those arkdep-variants could use some love, they’re all not synced with the official test-manjaro-gnome image, at least afaik.
So far i like it.
regards
sudo nano /arkdep/config
I’ll look in to that.
To an extend it is, we should support all the common apps which have a sizable userbase. I am still on the fence about DisplayCal + argyllcms
, it seems to be more pro-creator focused than at normal desktop users.
But including something like libratbag
out of the box makes a lot of sense.
For more specialized usecases, such as pro-creator, it indeed makes a lot more sense for the community to pick up the mainenance of their own images. They can then specialize these images and configure them with all their tooling out-of-the-box.
nano is not installed & I can’t see it in the software centre. The only thing there was nanonote & that did nothing. Terminal says Sudo: nano: Command not found
Looked at my ‘normal’ Manjaro & it has nano & nano-syntax-highlighting installed but they are not in the immutable OS. At least I can’t find them.
Think I might have to give up on this. I’ve been trying different things for at least four hours just to edit one file.
Thanks anyway. You to @RazorClaw