On Sun, Dec 6, 2020 at 7:37 AM Neil Bothwick <n...@digimed.co.uk> wrote: > > Maybe the devs need to rename the systemd-tmpfiles package to satisfy > those that break out in a sweat at the mention of the s-word :)
Or maybe people who care a great deal about the filenames of stuff just could rename them as they prefer? :) And if the part you don't like is what website or tarball the source is distributed from, well, it is FOSS so you can always just host it yourself. opentmpfiles is just a reimplementation of systemd-tmpfiles in bash with the goal of running on platforms that don't support linux syscalls (and I guess bash makes everything better cause C became corrupt the moment Lennart learned how to program in it...). So, if systemd-tmpfiles does something you don't like, chances are it is just a matter of time before opentmpfiles does too. I think the idea of having something more cross-platform is a good one, though there is nothing really about systemd that isn't "open" - it is FOSS. It just prioritizes using linux syscalls where they are useful over implementing things in a way that work on other kernels, which is more of a design choice than anything else. I mean, it is no more wrong to use linux-specific syscalls than for the linux developers to create them in the first place. In some situations the linux-specific stuff lets things be done that aren't practical with pure POSIX and safer manipulation of links is apparently one of them. Really what probably wouldn't hurt is some kind of FOSS POSIX-extension effort that tries to standardize stuff like this so that it can be implemented across other kernels in a standard way, at least for things like this which seem really useful. I suspect that the systemd folks might be willing to accept cross-platform improvements if it were practical to do so, and if not you could always fork it. -- Rich
