XR for Universal Blue and Fedora Atomic Desktops
vr
fedora-atomic
linux
Update migration guide
+9
-25
+9
-25
README.md
+9
-25
README.md
···
14
14
15
15
## Auto-migration script ##
16
16
17
-
This script will walk you through the migration process:
17
+
This script will automatically remove AtomicXR and install the new software:
18
18
`bash -c "$(curl -fsSL https://tangled.org/matrixfurry.com/atomic-xr/raw/main/migrate.sh)"`
19
19
20
-
If you'd like to learn more about the changes and why they were made, please read the next section.
21
-
22
20
## Changes ##
23
21
24
-
The script will walk you through what has changed, but if you want to learn more about *why* things have changed, this
25
-
is the section for you.
22
+
I recommend reading this section, but here's the TL;DR:
23
+
- Run the above migration script
24
+
- Envision-OCI is much easier to use. Just install it and start Envision as normal, everything else will
25
+
be handled automatically. No more building from source or "Launch in Build Mode" required!
26
+
- AtomicXR CLI's manual system configuration commands are no longer necessary
26
27
27
28
### 1. The AtomicXR Homebrew Tap has been replaced by Homebrew-XR
28
29
···
35
36
36
37
### 2. Envision in Distrobox (`axr envision`) has been replaced with Envision-OCI
37
38
38
-
The old process for getting Envision to build software inside a container was complex, hard to understand, and very
39
-
prone to breaking.
40
-
41
-
When Envision was installed or updated via the AtomicXR CLI, it would:
42
-
1. Create a Fedora Distrobox container, then manually install all the build dependencies for Envision, Monado, WiVRn, WMR, etc.
43
-
2. Delete any previously installed build of Envision and start from scratch
44
-
3. Download the Envision source code and apply patches for the homebrew plugin system
45
-
4. Create an entirely separate "build mode" that runs envision itself in the Distrobox container
46
-
5. Build Envision from source
47
-
48
-
That approach caused countless bugs and hard-to-understand issues for people. Runtime libraries would be missing on the
49
-
host, Envision sometimes wouldn't launch outside of build mode, builds would randomly fail, Monado couldn't run inside
50
-
of build mode, etc.
51
-
52
-
Maintenance was also very tedious and difficult. Anytime something was updated or fixed, more bugs
53
-
would appear. Eventually, it got too out of date, and no longer could install or run at all.
54
-
55
-
Luckily, you don't have to worry about any of that anymore. Envision-OCI takes a much simpler approach, it uses a
56
-
shim to run builds in Podman, using pre-built container images that include all the required build dependencies. All it
57
-
needs to work is a modified PATH containing the shim, no more or building from source or "Launch in Build Mode" required.
39
+
The old process for getting Envision to build software inside a container was complex and very prone to breaking.
40
+
Envision-OCI is much easier to use. All you need to do is install it and start Envision as normal, everything else will
41
+
be handled automatically. No more building from source or "Launch in Build Mode" required!
58
42
59
43
Pre-built Monado packages will also be available soon in the Homebrew-XR repository. Most people won't need to worry about
60
44
building it themselves. You'll be able to install Monado in seconds, and use Envision as an easy launcher and configuration tool.