rename/rebrand get_ostree_deps

[cgwalters]

I'm trying to make ostree just a backend for bootc first of all.

But in general I don't think we need any branding for these dependencies at all...can't we call this script get-runtime-deps or so?

[richm]

But in general I don't think we need any branding for these dependencies at all...can't we call this script get-runtime-deps or so?

We can change the name. We'll discuss this with the team.

We're in the process of allowing all of the system roles to be able to be used at bootc build time, and possibly in other image building contexts - see linux-system-roles/cockpit#212 - so we won't need to use the script for bootc, but possibly for other contexts.

I'm trying to make ostree just a backend for bootc first of all.

One of the key things that every role must to is to determine if the system is image mode or not e.g. https://github.com/linux-system-roles/firewall/blob/main/tasks/firewalld.yml#L8 by looking for the file /run/ostree-booted - the role must know if /usr is writable, primarily for the package management - https://github.com/linux-system-roles/firewall/blob/main/tasks/firewalld.yml#L36 - is there some work I can follow so that I can change this mechanism in the system roles when it is available?

[richm]

@cgwalters what about if we rename ostree to immutable_os? so get_immutable_os_data.sh and README-immutable-os etc.? or even readonly_os?

One of the important things the roles need to know is how to determine if the system is immutable/readonly - the way we do that now is with /run/ostree-booted

[cgwalters]

@cgwalters what about if we rename ostree to immutable_os? so get_immutable_os_data.sh and README-immutable-os etc.? or even readonly_os?

Sure, but what about my suggestion of get-runtime-deps?

One of the important things the roles need to know is how to determine if the system is immutable/readonly - the way we do that now is with /run/ostree-booted

bootc-dev/bootc#1661

[richm]

@cgwalters what about if we rename ostree to immutable_os? so get_immutable_os_data.sh and README-immutable-os etc.? or even readonly_os?

Sure, but what about my suggestion of get-runtime-deps?

IMO "runtime deps" is not specific - this is specifically for the runtime deps for building images for immutable operating systems when packages cannot be installed at runtime by the role.

One of the important things the roles need to know is how to determine if the system is immutable/readonly - the way we do that now is with /run/ostree-booted

bootc-dev/bootc#1661

What if a system has an ostree backend but isn't using bootc? Will we still be able to rely on the presence of /run/ostree-booted?

[cgwalters]

IMO "runtime deps" is not specific - this is specifically for the runtime deps for building images for immutable operating systems when packages cannot be installed at runtime by the role.

Even for a package-based mutable system, I still might want to have expected content pre-installed in my kickstart or blueprint instead of later installed dynamically.

Think of it like Requires: from RPM (or equivalent from dpkg etc)

What if a system has an ostree backend but isn't using bootc? Will we still be able to rely on the presence of /run/ostree-booted?

Yes.