nina
> > can't one load/parse the whole dependency graph before actually starting anything? > > The difficulty is that a service named in a `before =` might not exist in...
sounds good then, that would cover everything at the moment
wouldn't one get `after` pretty much for free once `before` is implemented without introducing much complexity? i don't strictly need it for things to be functional right now, but I...
If the named service does exist, `after` is not equivalent to `waits-for`, as `waits-for` will result in the named service being activated. I'm not sure I understand why you can't...
already deployed it, works like a charm
The reason the dependency is bumped is the migration to `GUri`; `SoupURI` is gone in libsoup3, and the copy-pasted `SoupURI` inside the codebase appears to be pretty much a workaround....
I thought distros in general used libsoup for ostree, but as it turns out Fedora/RHEL does not, so it should be practical for things that do not switch flatpak to...
yes, indeed - i was thinking those could switch to curl backend for the time being, or alternatively carry a patch for flatpak (there is already an open pull request...
I added back support for libsoup2; it can be enabled with `--with-soup2`. The higher GLib requirement is still in place (I will try to get it down to 2.66 though)...
changed minimum glib version to 2.66; updated the GUri code to only use the 2.68 scheme normalization when new enough and otherwise it normalizes manually