Conversation
Signed-off-by: Sam Day <me@samcday.com>
Signed-off-by: Sam Day <me@samcday.com>
Signed-off-by: Sam Day <me@samcday.com>
Signed-off-by: Sam Day <me@samcday.com>
940f700 to
446906e
Compare
|
@agx here's the not-Meson approach I had in mind when we last discussed this stuff a few weeks ago. Since I maintain the Fedora+Alpine packaging downstream, I'm already mostly happy with the shape of this. I'm curious what you think about the Debian side, though. Is there a canonical way that Debian prefers to see these generated/templated artifacts handled? I want to make sure this isn't going to cause problems for the official Debian packaging downstream later, nor the Phosh nightly repo. |
|
That's certainly an improvement as we can get rid of the per distro greetd configs. 👍 It doesn't strike me as elegant as the (or other build system triplet invocation) approach as the later would also make it simple to place the files in an installed tree (thus removing the EDIT: …and it certainly will work for Debian / nightlies |
No description provided.