distribution packages

[ddiss]

Now that we've started moving away from magic paths in the rapido directory for rapido.conf and initramfs image output, we can probably consider providing rapido as a distribution package (while retaining all run-from-git-dir functionality). There are still a few things which I think should be cleaned up before we do go down that path though. First things that come to mind:

• rapido.conf default search paths should probably include a path under $HOME (and perhaps /etc too)
• initramfs images should be output in the current working directory by default(?)
• rapido boot should accept an initramfs image path parameter

[ddiss]

I've published RFC packages at https://build.opensuse.org/package/show/home:dmdiss:rapido/rapido .
@Werkov you may be interested in pulling these into your container for testing.
There are a number of changes atop the current master branch which I'll submit as an RFC pull request for discussion. The main reason for keeping it RFC is that the default path decisions should be carefully considered.

[Werkov]

Invoking rapido (relying on PATH and /usr/bin/rapido) won't properly initialize RAPIDO_DIR (e.g. rapido list returns empty list of available cuts).
Calling /usr/libexec/rapido/rapido works.

[ddiss]

Invoking rapido (relying on PATH and /usr/bin/rapido) won't properly initialize RAPIDO_DIR (e.g. rapido list returns empty list of available cuts). Calling /usr/libexec/rapido/rapido works.

/usr/bin/rapido is a symlink to the libexec binary path, so RAPIDO_DIR should be properly initialized given that realpath is used. I'll take a closer look. Thanks for the feedback.

[ddiss]

Invoking rapido (relying on PATH and /usr/bin/rapido) won't properly initialize RAPIDO_DIR (e.g. rapido list returns empty list of available cuts). Calling /usr/libexec/rapido/rapido works.

/usr/bin/rapido is a symlink to the libexec binary path, so RAPIDO_DIR should be properly initialized given that realpath is used. I'll take a closer look. Thanks for the feedback.

Yep, you're right, it's broken. This can be fixed via:

 15 RAPIDO_DIR="$(realpath -e $BASH_SOURCE)"
 16 RAPIDO_DIR="${RAPIDO_DIR%/*}"

...but I'm wondering whether the whole RAPIDO_DIR relative-path calculation should just be dropped in favour of hardcoded paths (with fallback to working directory for git repo).