On Mon, Feb 1, 2016, at 16:41, Josh Triplett wrote: > Implementing the various operation letters makes up half the problem. > The other half involves handling the various tmpfiles.d directories and > the precedence between them. That includes the usual "override files > with the same filename" mechanism, but also: > > > All configuration files are sorted by their filename in lexicographic > > order, regardless of which of the directories they reside in. If > > multiple files specify the same path, the entry in the file with the > > lexicographically earliest name will be applied. All other conflicting > > entries will be logged as errors. When two lines are prefix and suffix > > of each other, then the prefix is always processed first, the suffix > > later. Lines that take globs are applied after those accepting no > > globs. If multiple operations shall be applied on the same file, (such > > as ACL, xattr, file attribute adjustments), these are always done in > > the same fixed order. Otherwise, the files/directories are processed > > in the order they are listed. > > That logic seems relatively straightforward (though fiddly) to implement > in a language with associative arrays, such as bash or Python, but not > in a language without them, such as POSIX sh.
While it would be ideal to a 1:1 perfect implementation, I would be a just happy with a simple constrained implementation that would work in "most" cases. + document that properly in manpage and README.Debian in that package. But of course I would not prevent anybody to do a full implementation :) (This also applies to your other email you sent meanwhile I was writing this.) Cheers, -- Ondřej Surý <ond...@sury.org> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server _______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
