Hi @ttuegel, freeze is soon https://discourse.nixos.org/t/nixos-20-03-feature-freeze/5655.
I don't see too many blockers here, do you need this in 20.03?

How about giving the 5.18 beta a try to see if that solves your problem? We could then skip straight to that when it's released in a weeks time.

How about giving the 5.18 beta a try to see if that solves your problem?

The problem is almost certainly a missing runtime dependency. Going up a version is likely to introduce more missing dependencies. 🙁

EDIT: Also, Plasma betas are closed, and I have neither the time nor the inclination to jump through the hoops necessary to get access.

I don't see too many blockers here, do you need this in 20.03?

Yes, I plan to get this merged before the feature freeze for NixOS 20.03.

Well, the plasma-workspace build system appears to assume it's running in a Wayland or X session, so I hope that's not critical for the build... 🤦‍♂️

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/nixos-20-03-feature-freeze/5655/22

The blocker is fixed. The non-blocking issue, I realized, is due to some changes not being ported from the start-up script to the new C++ executable. I think it is appropriate to move those to the NixOS Plasma 5 start-up script, instead of the plasma-workspace package, because they are NixOS-specific. Although these are non-blocking cosmetic issues, I would still like to deal with them before merging.

The blocker is fixed. The non-blocking issue, I realized, is due to some changes not being ported from the start-up script to the new C++ executable. I think it is appropriate to move those to the NixOS Plasma 5 start-up script, instead of the plasma-workspace package, because they are NixOS-specific. Although these are non-blocking cosmetic issues, I would still like to deal with them before merging.

I believe such a change would qualify as a bugfix so you have during beta to produce such a change.

I believe such a change would qualify as a bugfix so you have during beta to produce such a change.

Yeah, you're right. I don't like merging something that I know is buggy, but at least merging this part reduces the bus factor.

I believe such a change would qualify as a bugfix so you have during beta to produce such a change.

Yeah, you're right. I don't like merging something that I know is buggy, but at least merging this part reduces the bus factor.

I opened an issue in the tracker so it doesn't get lost.