swupd assumes Clear Linux as a host OS and hard-codes several paths to directories, programs and configuration files on Clear. Create patches to make these paths configurable and submit them upstream.
Shouldn't this be a bug against swupd? It's not clear to me if it intentionally assumes CL, but I think it shouldn't.
(In reply to comment #1) > Shouldn't this be a bug against swupd? > It's not clear to me if it intentionally assumes CL, but I think it > shouldn't. Yes, it should. IIRC there wasn't a public bug tracker at the time so this seemed a good place to keep track. Upstream bug filed: https://github.com/clearlinux/swupd-client/issues/67
Patch submitted upstream: https://github.com/clearlinux/swupd-client/pull/71
Waiting For Upstream status is being removed, changing to Accepted.
This was partly addressed. Upstream is tracking the rest at https://github.com/clearlinux/swupd-client/issues/208
Upstream swupd has changed a lot and integration with the Yocto Project would be tricky and need rework to the layer. Closing this as obsolete since any new integration would need rework and have its own issues.