/etc/os-release variant alt about yadm HOT 3 CLOSED

yadm.distro_family is populated via the ID_LIKE value in /etc/os-release.

Do you think it would help to do something like this:

• Set a local class value within your bootstrap by running
  • yadm config local.class $(awk -F= '$1=="VARIANT_ID" {print $2}' /etc/os-release)
• And then use yadm.class in your template?

from yadm.

Thanks for the reply @TheLocehiliosan

While I did not use the solution you proposed it nudged me in the right direction.

After some tinkering I landed on the following solution, which also allows me to rebase my silverblue to kinonite for example. I switched to esh for templating and I think it also makes it easier to document why there is an if:

# WARNING: Do not edit this file.
# It was generated by processing <%= $YADM_SOURCE %>

<% if type rpm-ostree > /dev/null; then -%>
# On rpm-ostree based systems rewrite the npm prefix to avoid trying
# to write to a read only mount.
prefix=<%= $HOME %>/.npm-global
<% fi %>
progress=false

from yadm.

Ah yes. That's a good solution and does make it more clear why that system is treated differently.

The "built-in" templating is very basic and really meant to allow some templating without much need for dependencies. But if you can use a more capable template processor it will open up the possibilities. 👍

from yadm.