Pavel Valena
Pavel Valena
Rebased, fixed as suggested. Sorry it has taken so long :).
From the reproducer I got, I can't tell, I'm afraid -- I suspect it's just a dummy one; from the reporter: ``` Create a fake library path: ~~~ # mkdir...
With the latter one, do you mean something like(?): ```yaml prepare: how: update ```
For the `dnf update` (or alike) implementation itself, I'd be fine with `--skip-broken` (IOW, best-effort). I'm not sure about `--nobest`, which actually completely excludes versions with broken dependencies, which may...
Some idea to consider, while implementing this: https://github.com/psss/tmt/pull/701#issuecomment-817864920
I'd prefer to avoid this, as the runtime can modify those cloned-out repositories, right? If one runs `make`, in some prepare phase, and it runs in that directory, it's contents...
> Would be nice to unify somehow the directory structure for saving such data, feels a bit like rpms, maybe other artifacts needed by other steps could share this unified...
Let me reiterate, in case I didn't write it clearly enough in my previous comment: - In general this is a good idea - please do not use symlinks -...
Maybe we should write some general information somewhere (man page?) that dracut basically sources the config files, so any env. variable can be "dropped in" as a configuration... It sounds...