toolbox/playbooks
Debarshi Ray df22010e4f playbooks: Use the same commands as mentioned in the documentation
... at https://containertoolbx.org/install/

There are some minor benefits to always invoking meson(1), as opposed to
directly invoking the underlying build backend, like 'ninja'.

It's one less command to be aware of.  Secondly, in theory, Meson can be
used with backends other than Ninja (see 'meson configure'), even though
Ninja is the most likely option for building Toolbx because it's only
supported on Linux.

https://github.com/containers/toolbox/pull/1142
2022-10-21 20:23:34 +02:00
..
build.yaml playbooks: Use the same commands as mentioned in the documentation 2022-10-21 20:23:34 +02:00
dependencies.yaml playbooks: Split out the dependencies into a separate file 2022-08-31 12:46:44 +02:00
setup-env-migration-path-for-coreos-toolbox.yaml playbooks: Make all Meson warnings fatal 2022-08-31 19:35:05 +02:00
setup-env.yaml playbooks: Use the same commands as mentioned in the documentation 2022-10-21 20:23:34 +02:00
system-test.yaml playbooks: Unify test setup for system & unit tests 2021-10-22 16:43:38 +03:00
unit-test.yaml playbooks: Use the same commands as mentioned in the documentation 2022-10-21 20:23:34 +02:00