Commit Graph

9 Commits

Author SHA1 Message Date
Arcitec
cec73978cf fix!: move justfile to standardized, non-conflicting new location
- The old location was conflicting with upstream images (main, nvidia, etc), and was causing the file to be overwritten.

- It was therefore decided that each image should prefix their own justfile names, to avoid clobbering, to easily allow image makers to bundle multiple "modular" justfiles, and to allow end-users to easily include the particular modules they want.

- The name `custom.just` represents a "template name" for this "custom uBlue image", while being neutral enough to use long-term (unlike the alternative name `startingpoint.just`, which doesn't flow nicely).

- All redundant commands that already existed upstream in `ublue-os/main` have been removed, to follow the new "modular inclusion" nature of uBlue's "justfile" organization, which also means that we'll never have to manually update it to match upstream anymore. No more duplicated effort! ;)

- Updated README instructions to mention the new way of including justfiles, until the upstream "just" project has finished their "include" functionality.

- The ".just" suffix is the official upstream suffix for modular justfile inclusions.
2023-05-14 18:18:18 +03:00
Arcitec
2f85593176 feat: include flowchart graphic which explains new launcher hierarchy 2023-05-14 18:18:18 +03:00
Arcitec
abbb283dbe fix: improve "yq" arguments in justfile
No more pipe redirection. We tell yq to read the file itself. And we use `--` to ensure it never interprets files as flags.
2023-05-14 18:18:18 +03:00
Arcitec
c4b6b47606 fix: switch profile.d script to more robust technique
- Now uses `sh`-style single-bracket `[]` POSIX syntax instead of the truly old-school `test` syntax. Both are equivalent and equally portable. In fact, `man test` explains everything that `[]` can do.

- We now symlink the user's autostart file to the uBlue image's own file, and we do it in a backwards-compatible way which replaces the user's current legacy script file (if any). The previous system dumped a permanent file in the user's home-directory which never updated again after that, which meant that OS updates could never fix or improve the autostart scripts in the future. That's now possible, thanks to being a symlink.

- If the user uninstalls uBlue, or switches to a flavor without `yafti`, then the leftover "autostart" symlink will simply be a minor nuisance that only causes some soft, invisible syslog warnings about the "broken symlink", which is an improvement over the previous system which kept a full `.desktop` file that attempted to run a binary and failed to find it.
2023-05-14 18:18:18 +03:00
Arcitec
ec4d01caa8 fix!: enhanced autostart.desktop to use new script, and always find icon
Notable changes:

- The icon is no longer dependent on "GNOME Terminal" being installed. Will now work on any desktop environment, not just GNOME. We only see this icon in "GNOME Tweaks: Startup Applications" or similar autostart-managers, which is even better reason to use a generic, always-existing icon for the shortcut.

- Now runs the new "autostart.sh" yafti GUI launcher.

- Tells the OS to not spawn a terminal window when running this shell script.
2023-05-14 18:18:18 +03:00
Arcitec
8a5fd31f88 feat: new "autostart" binary, for easy startup customization
Instead of having to use a restrictive command-line in a ".desktop" file, we are now able to use scripting to create more advanced launchers, or if someone wants to easily switch yafti to something else.
2023-05-14 18:18:18 +03:00
Arcitec
34f6189d26 fix!: move all autostart-related files to standardized location 2023-05-14 18:18:18 +03:00
Arcitec
8ee996722f fix!: move yafti.yml to standardized location 2023-05-10 21:44:01 +03:00
Arcitec
07642c2f43 fix!: move justfile to standardized location 2023-05-10 21:44:01 +03:00