I tried to install `Minecraft` through Omarchy's menu, however it fails
with the following error message:
error: target not found: minecraft-launcher
This occurs because, according to Arch's documentation, the package is
available through AUR rather than the official repositories.
Reference: https://wiki.archlinux.org/title/Minecraft#Installation
* install ollama from the official website
* installing ollama-cuda if nvidia-smi exists
* add check for rocminfo installation for AMD GPUs
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
As well as installing the `emacs-wayland` package, we enable and start
the `emacs` systemd service. A GUI Emacs client can then be started
using e.g. `emacsclient -c`.
* Allow failed migrations to be skipped
Failed migrations can be now be skipped by a prompt. This means that if
a migration is "stuck" then a user can opt to store it in a separate
skipped directory. Skipped migrations will be considered for the
purposes of running the pending migrations, however in future, we can
allow the user to run their skipped migrations with a flag.
To allow the script to continue and prompt for failed migrations, the
`set -e` has been removed. A manual check on the exit code is used
instead.
* Cleanup implementation a bit
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
When running `laravel new`, if a starter kit like `React` or `Vue` are
selected, the installer will ask:
```
Would you like to run npm install and npm run build?
```
And in order for it to work, `npm` should be available.
Having this installed will definitively smooth out the experience from
install to up-and-running!
* Get rid of -Sy and -Syy
* Get rid of all naked -Sy usage
* Don't need a full system update for this
* Combine
* Does not need a full system update
* Need to refresh even just for Omarchy repository
* Does not warrant a full system update
* No longer need the sudoless pacman runs
* We have already added the Omarchy repo before getting to here
So fine to just do a straight install
* Don't update system packages to prevent issues from something too new at the wrong time
* Add system to pin and ignore bad packages
To deal with the abseil-cpp issue
